However, we're having trouble linking to a Paradox table from Access 2007.
Sometimes we can do it. Other times Access announces a network
initialization error (11265).
Whether we get this or not is related in some way to whether we've run our
D7/BDE application since we booted Vista. So, we suspect some registry entry
or BDE configuration issue.
Anyone have any suggestions (other than the not-possible, but coveted
"Abandon the BDE")!
Thanks
And, BdeAdmin.exe was locking up when closing. (It may still be for all I
know... I'm not using it!)
Use RegEdit to change the key below to a folder to which you have full
rights:
HKEY_LOCAL_MACHINE\Software\Borland\Database
Engine\Settings\Drivers\Paradox\Init\NetDir
Both methods, however, also lock up after making the change, looping
(according to a registry monitor I'm running) on changing a registry
variable related to Date. But, before locking up, they make the change.
To avoid the lockup, run BDEAdmin as Administrator (by right clicking on the
exe.)
I also noticed in my registry monitor Access querying the registry for NET
DIR in a registry location under Office, ... Access Connectivity engine, and
not finding it. I don't know anything about this registry entry or how it
is used. But it doesn't seem to be needed here...
can you give me some step by step info on how to bypass vista c:
constraint for pdoxusers.net
thanks in advance
vista ultimate user
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
> can you give me some step by step info on how to bypass vista c:
> constraint for pdoxusers.net
Try putting pdoxusrs.net in the All Users\Application Data directory.
--
Bill Todd (TeamB)