error "bad file name or number" 1

[Guest_imported]

We have an Access97-database with some forms running on a windows95-platform and never had any trouble with accessing drives ( local or network ) in the Access-application. Since we switched over to Windows2000 as OS, we always get error "bad file name or number" when we want to view a network drive. This problem does not occur when we go to local harddrives or a local CD-romstation.

This is a piece of the code :

"
Private Sub CmbDriveBron_AfterUpdate()
On Error GoTo Err_CmbDriveBron_AfterUpdate

DirStringBron = Me!CmbDriveBron & ":\"
Me!Text11 = DirStringBron
Me!List4.Requery

Exit_CmbDriveBron_AfterUpdate:
Exit Sub

Err_CmbDriveBron_AfterUpdate:
MsgBox Err.Description
Resume Exit_CmbDriveBron_AfterUpdate

End Sub

"

We see that Access doesn't generate any error and that the system crashed on the "Me!List4.Requery"-command.

Does anybody have an idea what the problem may be ?

 

[jimmythegeek]

Have you tried using the whole UNC path? This will guarantee that anyone on the network will see the same location as opposed to the fact that one person's G:\ drive could be pointed to a share that is not the same as someone elses G:\ drive.

For instance, lets say your server is called ProdServ01, instead of using:

G:\Databases\MyDb.mdb

you would use:

\\ProdServ01\Databases\MyDb.mdb

Dont' know if this will solve your problem, but a good practice to use nonetheless. Jim Lunde
compugeeks@hotmail.com
We all agree your theory is crazy, but is it crazy enough?