Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Paradox 8 BDE Error on Windows XP

Status
Not open for further replies.

Mtneer

IS-IT--Management
Apr 1, 2002
6
US
I'm running Paradox 8 on a Windows XP machine with NEtWare client 4.83.

I can't run Paradox - I get the dreaded "Network initialization failed - Cannot access network lock file - Cannot initialize BDE" error.

I have all of my users pointing to the same directory on a NetWare server that they all have full rights to. All of the users can run Paradox ok - it's just me on my XP machine that doesn't work.

Verified that I have no stray PDOXUSRS.NET or PARADOX.LCK files on the network drives or on my PC.

Any ideas? TIA.
 
I have been having problems with XP too. Make sure that you have permission to access your default WORK directory. Also, are you able to open the IDAPI.CFG file with the BDEadmin program?

Mac
:)
mailto:langley_mckelvy@cd4.co.harris.tx.us
 
Yes, I have full rights to my working directory. (I'm the network administrator - I have supervisor rights to everything.

I can open the idapi.cfg file with the BDE. I tried pointing it to another directory, saving it, them coming back and pointing it back to the correct directory and saving it again to make sure that it was accepting changes. It was. It's all very strange.
 
That is bizarre, but nothing about XP surprises me anymore. I'm also the admin, but if I'm not logged in to my XP machine as ADMIN, I can't set permissions for my own hard drive under my network username :(

Every problem I've encountered with Paradox and XP has to do with permissions. Have you tried kicking everyone else off, deleting the common NET file and _then_ trying to start Paradox?

Mac
:)
mailto:langley_mckelvy@cd4.co.harris.tx.us
 
This is hardly a solution, but backing down to version 4.82 of the NetWare client resolved the problem.
 
Odd..., but netware clients have caused me problems in the past also - particularly involving user identity obtained via Pdox.

I'll keep it in mind in case I have a similar problem.

Mac
:)
mailto:langley_mckelvy@cd4.co.harris.tx.us
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top