BorlandTalk.com

Tom · Guest

Using the BDE/Paradox with Vista RTM seems to be working fine for us so far.

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

Tom · Guest

Further details on our problem: We seem to be always able to *open* a table
that was previously linked, but actually linking table for the first time
usually generates the 11265 error.

Tom · Guest

The problem I was having opening Paradox files in Access 2007 were due to
the fact that the (default) BDE NetDir (for PdoxUsers.Net) is C:\, which is
a restricted location in Vista.

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

Tom · Guest

Follow-up for anyone needing this information: I, of course, was wrong
about using the registry to change NET DIR. It's in IDAPI32.cfg and can only
be modified by BDEAdmin.exe or DBI calls. Both of these access methods allow
you to change Drivers, Native, Paradox, NET DIR (with a space in the middle)
to a folder other than the Vista-protected C:\, preferably to the same
folder that your app sets Session.NetDir to.

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...