- Computers & Software
PowerBuilder Database Management System - Data Installation Procedure for a PowerBuilder Database Application Program
If your computer suddenly crashed and you happen to be using a database application which was originally developed and deployed using PowerBuilder by Sybase and you can't seem to locate the original programmer who wrote the scripting code and who also implemented the application program into your company database system, and the worst part is you don't have the slightest idea about creating a database or how data management works, then you run the risk of losing all your important data accumulated over the years. But before you take any drastic actions you might want to sort things out a bit and try to analyze the problem from a different perspective. If you happen to be wise enough to have a backup copy of the implemented application for your company database system then all you need is the following instruction to reinstall your PowerBuilder database application program.
A side-note: The following instruction is intended for database programs
developed using PowerBuilder which uses Microsoft Access database as the main
data handling container.
Procedure: Majority of these Database Applications developed using PowerBuilder may actually be working together in conjunction with Microsoft Access to make up a whole functioning application. You may find a Microsoft Access database file contained inside the folder of your PowerBuilder Database application program which came along with your PowerBuilder executable file. And there are also instances wherein majority of the user interface for data entries into this Microsoft Access database container were designed specifically to receive data entries from users who have proficient familiarity in using Microsoft Excel instead of Microsoft Access, resulting in the development of a complete PowerBuilder database application that accepts data inputs coming from Microsoft Excel files which is then automatically imported to the Microsoft Access database container file where the user data entries from the Excel files are stored, and which in turn is retrieved by the PowerBuilder database application program to generate the data output. Regarding the software file linkage between Microsoft Excel to Microsoft Access for the PowerBuilder Program, please follow the succeeding outlined instructions below. The following is a detailed step-by-step guide for the installation and setup of the PowerBuilder database program to the computer.
Be aware of the following notes:
NOTE 1: Maintain religiously a backup copy of the PowerBuilder database management system program by copying the entire folder of the database application program to another safe location such as a USB flash drive or to another computer or to your portable backup hard drive for safekeeping and for later retrieval. Always make a backup file of the database management application program's file folder on a regular basis since the folder would most certainly be populated with daily data entries over time.
NOTE 2: Make sure that any computer that will run the PowerBuilder application program containing your database management system belongs as a member of your internal network which will have to be correctly setup to work with your currently active workgroup name, check and verify the active workgroup name of the currently maintained network from any of your networked computers with a working network connection.
File association between Microsoft Excel and Microsoft Access Application Files and the PowerBuilder Application Program:
If the target computer which will run the PowerBuilder database application program does not already have a copy of the database folder which contains all the relevant files for the database application program, then place a copy of the database application folder to the target computer, place it in drive C.
Open the Control Panel | Administrative Tools | Data Sources (ODBC) |
Under User DSN tab, click "Add".
In the "Create New Data Source" dialog box, select "Microsoft Access Driver (*.mdb)", then click "Finish".
In the "ODBC Microsoft Access Setup" dialog box, type the executable file name created for your database (e.g. query1 or could be Query1 depending on how it was originally declared) in the "Data Source Name".
Under "Database" click the "Select" button, then locate the directory of your database application folder in drive C of the local computer, then locate and select the Microsoft Access database file "something.mdb" which can be found inside the database application folder in drive C of the local computer.
Click OK -> OK -> OK to close the 3 dialog boxes.
Close the Control Panel.
Open the database management system application folder in drive C of the local computer, then open the Microsoft Access file "something.mdb".
In the database window of your Microsoft Access database system, under Objects -> Tables -> right-click any linked excel table file previously linked from other computers in your office network, righ-click any one with the excel icon, then select Linked Table Manager from the pop-up box, then place a check on the box next to "Always prompt for new location", then click theSelect All button, then click the OK button.
A dialog box appears that allows you to re-route all your existing linked Excel files to a new location of your choice, for example: if you are running the database application program from computer-A and the related excel files are located in computer-B, then navigate to the appropriate location or path of the correct directory which contains all relevant excel files in computer-B (e.g. something.xls).
Save and close the Microsoft Access file “something.mdb”.
Run the PowerBuilder executable file located in the database application folder, the PowerBuilder database application program should now be working.
I, the copyright holder of this work, hereby publish it under the following license:
PowerBuilder Database Management System - Data Installation Procedure for a PowerBuilder Database Application Program by ianjonas is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License.