Unless you mean you want an icon on your operating system which starts up a Progress/Openedge session. You need to be clearer with your requirement.
For example, on Windows if I wanted to start an OE10.1A session calling Main.p using MySettings.ini I would create a shortcut to run a .bat file which sets the required environment variables and runs prowin32 with the required startup parameters. The contents of my .bat file would look like this
Code:
SET DLC=C:\Progress\OE101A;C:\Progress\OE101A\bin
SET PATH=%PATH%;%DLC%;%DLC%\bin
C:
cd c:\Progress\OE101A\bin
start prowin32 -T %TEMP% -p C:\MyApp\Main.p -basekey "INI" -ininame C:\MyApp\MySettings.ini
The exact path of your DLC depends on your installation location, and if this is set up as an environment variable already, this is not required.
If you connect to an appsever, the appserver config can handle db connections.
If you are running client-server, the client connects straight to the database(s). This can be done with a CONNECT statement or using a parameter file (.pf) or both!
if suppose i have a db called as sample.db in my local machine and i want to update few tables with my program which i run through above .bat file .
Now , how can i connect to this db to make necessary updates in database .
So far you aren't being very forthcoming about what it is that you are really trying to do. The topic has now drifted from running a program to connecting to a database. You might get better results if you would carefully explain what you're trying to do rather than hoping that someone will read your mind.
If you are attempting to connect from within a .p look up the CONNECT statement in your documentation. The easy way to do that is to go to start -> progress -> help. Then click the "index" tab and type "connect". Then choose "connect statement". That will give you all of the syntax and some code samples.
If you need to connect with a command line (like in a .BAT file or on a shortcut's command line) then you can either just put the dbname after the executable name (use the full path) or you can use the -db startup parameter.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.