FiveTech Support Forums

This is a strange one and I hope someone has seen this before and can help....

In my app I open a file via \MyLocalPc\MyFolder\MyFile.dbf
This works on almost every computer I have installed my app on.

Here is the strange part.... One customer can open the file when they are connected to a network but not when they have no network connection.
Just to be clear, this file is local. My app is not trying to access any networked files on this system.

I can reproduce this on one of my laptops if I disable the network adapter.

Stranger still .....
If I type in the \MyLocalPC in explorer it will show me all the "shares". One of which is the folder where MyFile.dbf is located.
If I double click on MyFolder I get the typical windows network error.
Now, I enable the network adapter, go into the MyFolder and all is well.
I disable the network adapter again, while in the MyFolder and everything works.

If I change my code to open "C:\MyFolder\MyFile.dbf" everything works regardless of the network adapter being enabled or disabled (as would be expected).

I do have a reason for using the UNC type connection so switching to C:... is not an option.

Has anyone had this issue before ?
Any suggestions ?

Probably a DNS issue. You can try adding entry in hosts file.
Directory: c:\windows\system32\driver\etc\
Filename: hosts
Add this info: 127.0.0.1 MyLocalPc

I just thought of another option.
Use \localhost\MyFolder\MyFile.dbf instead of \MyLocalPc\MyFolder\MyFile.dbf

localhost should always reference local computer at address 127.0.0.1

Thanks Gale.

I would need to stick with the first option as I need the actual computer name

Unfortunately it didn't make a difference

I do have a reason for using the UNC type connection so switching to C:\... is not an option.

Hi James,

When my systems are networked there are data and report files that would be accessed by other systems.
If the system goes off-line then some files would need to be stored locally.

So, if let's say a report is stored and I save the file location to "C:\" when they are back on the network and a networked system tried to access the report it would look in C: on its own drive. No report would be found. If I use the Computer Name then there is no problem of opening the report from a networked system.

Also, some users want to keep the reports stored locally regardless if they are on the network or not.

I do have a routine that will move the reports to the network but for the users that keep reports locally using C: would cause issues.

Jeff,

OK. It seems your file access error problem is a Windows issue that may be difficult or impossible to solve (as evidenced by the fact that Windows Explorer has the same issue). So, I suggest checking for a network connection, then using a different path depending on the result. If you are using the SET PATH command, then this would be a very simple change.

James

how about using "net use" command?
So with network it is on drive f:
Without network use command below before your program
net use f: \MyLocalPc\MyFolder

Then when you run your program it is still looking for dbf on drive f: