Paradox not connecting to data on startup

[uighur1]

Our problem is that when we log onto the network, paradox creates an alias when referencing the local drive, the applications can find the data when directed to it manually and the script is run from there.... yet it cannot find the data/network at startup. This is not isolated to just one application using paradox, but rather affects all paradox apps. After mapping out the data path it runs fine, but it needs to be done manually after every restart, ie every morning...Does anyone know if Novell networks affect paradox in this way? Does anyone know if this issue is related to the working directory and or processing speed? Any feedback on this would be greatly appreciated....Thanks

 

[TonyMcGuire]

> After mapping out the data path it runs fine

What does this mean?

Do you create a map to the drive on startup of the computer?

> when directed to it manually

Huh?

If the workstation doesn't map the drive, the drive isn't mapped.

Please use different words to describe your situation. I, for one, don't understand the scenario or what is happening at all.


Tony McGuire
"It's not about having enough time; we have the rest of our lives. It's about priorities.

 

[Lewy]

I guess you mean that the data is stored on a mapped drive. For example the data resides in c:\pdox\data which has been mapped through windows as drive P. In the paradox BDE config you have pointed the data to P. When starting Paradox for the first time you are having to manually map drive P to get Paradox to see the data, otherwise you get an error message.

This also happens to me using the simple? windows xp networking!! Allthough not every morning. I have tried writing a simple bat file that will check for the mapped drive before opening Paradox but have yet to get it to work.

I hope this clarifies the situation Tony, any answers though!

Lewy

 

[TonyMcGuire]

What version of Windows?

You should be able to map a drive, and tell Windows to recreate it on startup.

One issue, on BOTH the 'server' and workstation. Make sure the network cards (NIC) are NOT set to allow the OS to put them to sleep. Can be defined in the properties for the NIC cards.

There is also the issue of good cabling, and using switches instead of hubs.

That's if I understand properly.

Tony McGuire
"It's not about having enough time; we have the rest of our lives. It's about priorities.

 

[TonyMcGuire]

What version of Windows?

You should be able to map a drive, and tell Windows to recreate it on startup.

One issue, on BOTH the 'server' and workstation. Make sure the network cards (NIC) are NOT set to allow the OS to put them to sleep. Can be defined in the properties for the NIC cards.

There is also the issue of good cabling, and using switches instead of hubs.

That's if I understand properly.

Tony McGuire
"It's not about having enough time; we have the rest of our lives. It's about priorities.

 

[Lewy]

WinXP home edition. I have just changed the NIC Card setting so I will see how things pan out.

Thanks,

Lewy

 

[jlockley]

Late for you, but I suspect that this will resolve what you are experiencing.

http://www.tek-tips.com/viewthread.cfm?qid=1346688