G'Day All,

I've got a quirky app that uses paradox tables and I'm having trouble launching the working directory from a shortcut.
My shortcut looks like this:
Target: "C:\Program Files\Corel\Paradox 10 Runtime\Programs\pdxrwn32.exe" -w "C:\Program Files\%appfolder%\psi\menu.fdl" -q
Start in: "C:\Program Files\Corel\Paradox 10 Runtime\Programs"
The error is: Working directory is invalid or undefined.

Do I need to point the BDE property NET DIR to an ini or config file?
Any advice on launching a paradox working dir from the command line would be appreciated.

TIA
Wayne
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Wayne, IIRC there is a file in the root directory called pdoxuser.net which requires full access by the user. Wise won't capture it but you can work it into your installation perhaps if you get a clean machine and do the vendor install, then copy the .net file off somewhere for later use.

You have my sympathy packaging a paradox app. I did a few of those!
Answered 12/12/2007 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
Thanks Owen,

I've got a vm set with the vendor install but I'm unable to find the pdoxuser.net file. Does this get created when the app first fires up, or is it created when you install paradox10?
I believe I have to point the Net Dir property in the BDE to this pdoxuser.net file.

Thanks for your time; appreciate it,

Regards
Wayne
Answered 12/12/2007 by: WayneB
Blue Belt

Please log in to comment
0
Wayne, it's been a while since I worked with this stuff. It might be created after the app starts up since this is kind of a cache or data file for paradox. No idea what it stores there but it won't run without it. I think you should be OK to leave your shortcut working directectories the way they are. Again IIRC, but even moving the pdoxuser.net file to another directory (where the EXE is) won't work. It's just a feature of paradox that the file has to be there in the root.

Good luck. If you run into further snags let us know. I'll search my feeble old memory if I can help [;)]
Answered 12/12/2007 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
Cheers Owen,
Unfortunately my vendor installation instructions aren't very clear, so when I get that working; I'm sure to find the pdoxuser.net file.
I love these server\ client type apps; they can be real...er..chewy[8D].
Regards
Wayne
Answered 12/12/2007 by: WayneB
Blue Belt

Please log in to comment
1
Unfortunately my vendor installation instructions aren't very clearShock!

Use the file BDEADMIN.EXE in the Borland common files folder (by default, 'C:\Program Files\Common Files\Borland\BDE'). Somewhere in there (I can't recall the exact detail) you need to configure the 'Native' Paradox driver's 'NET FILE' parameter. Set the folder to somewhere where users will have write access (IIRC, we used [ALLUSERSPROFILE]\Application Data\Borland\BDE - which we created in our MST) then save the configuration file. If you are (or the vendor is) using the BDE merge module, you'll need to copy or merge the resulting CFG file in the MST, too. The application will create the PDOXUSRS.NET file in that location if none exists.

You may also need to permission the default BDE folder, so that users can reconfigure such things for other Paradox apps (God help them...), although I believe the location for the CFG can be configured by a registry setting: I ran out of time to research that further before deployment time.
Answered 12/13/2007 by: VBScab
Red Belt

Please log in to comment
0
VB, I may save your post in case I ever have to package a paradox app again (heaven forbid)
Good Ideas that I don't remember trying the last time.
Answered 12/13/2007 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
Ian,
Thanks for the valuable information.
The cfg file is called idapi32.cfg for others reading this. Which is in the folder:
Program Files\Common Files\Borland Shared\BDE.
I'll repackage the app later today after I get in touch with the vendor about his sus tables which are thowing up a
"You do not have authority to access this software" error which I'm attributing it to the Hasp license.
Btw it looks as if I'll have to package the Paradox 10 install as well, yee ha!

Regards
Wayne
Answered 12/13/2007 by: WayneB
Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity