Hi,
I have Corel Paradox 9 running on my machine fine as a standalone app.
I need to access a database on another machine on the network. Thus I put the UNC path into the BDE settings which I can do running bdeadmin.exe. Then the wheels fall off.
There are various errors that occur but in the end the path is either 'invalid' if I try to set the path for the WORK directory, or we 'fail to initialise the BDE' when starting Pdox with the edited BDE settings. Is this likely to be some wine issue or should I look for some Paradox/BDE configuration error?
I am no longer certain about the latter possibility, I have other win machines doing this fine and have checked carefully but find nothing obvious.
thanks for any comment
Ian
Corel Paradox 9 network access
-
Ian Balchin
- Level 1
- Posts: 9
- Joined: Tue Jan 01, 2013 4:10 am
Re: Corel Paradox 9 network access
Hi, Dimesio,
Thanks for that response. I saw that and concluded that it was not relevant to the problem as I then saw it.
I was not intending to mount the share from the Win server onto my linux file system tree. Unless you commend me to do that I haven't see that as the way forward.
Any Paradox client running on a Windows box connects to the Win server simply using the UNC path specified in the BDE (Borland Database Engine) idapi.cfg file. No 'mounting' by win default. I still assume it should work this way under Wine.
I did create the directory structure ~/.wine/dosdevices/unc/myserver/mydir (no drive letter?) and indeed Paradox now starts up and I can set the appropriate UNC path as the WORK: directory but no data shows. In fact the apparent connection is a fiction, the 'set current directory as working directory' button is still greyed out.
So as I see it, we are not connecting through the network to the server despite having correct settings as far as Pdox is concerned. I can ping the server, I can access the filesystem using smbclient.
Any further comments welcomed. Tomorrow I will examine all things pdox on the existing system closely just in case.
bestest for 2013
Ian
Thanks for that response. I saw that and concluded that it was not relevant to the problem as I then saw it.
I was not intending to mount the share from the Win server onto my linux file system tree. Unless you commend me to do that I haven't see that as the way forward.
Any Paradox client running on a Windows box connects to the Win server simply using the UNC path specified in the BDE (Borland Database Engine) idapi.cfg file. No 'mounting' by win default. I still assume it should work this way under Wine.
I did create the directory structure ~/.wine/dosdevices/unc/myserver/mydir (no drive letter?) and indeed Paradox now starts up and I can set the appropriate UNC path as the WORK: directory but no data shows. In fact the apparent connection is a fiction, the 'set current directory as working directory' button is still greyed out.
So as I see it, we are not connecting through the network to the server despite having correct settings as far as Pdox is concerned. I can ping the server, I can access the filesystem using smbclient.
Any further comments welcomed. Tomorrow I will examine all things pdox on the existing system closely just in case.
bestest for 2013
Ian
