B
Brian
FE: MDE on five WinXP Pro, Access 2003 runtime PC's.
BE: MDB on Win2003 server
The path to the BE on my test system is different than the path to the BE
for the live users. When I distribute a new MDE, I trap an error on the first
attempt to contact the BE, and then re-link automatically. Here is the code,
in brief (omitting the dimensioning of some variables, etc.)
Set dbProgram = CurrentDb
For TableCount = 0 To dbProgram.TableDefs.Count - 1
If dbProgram.TableDefs(TableCount).Connect <> "" Then
dbProgram.TableDefs(TableCount).Connect = ";DATABASE=" &
FilePathData & ""
dbProgram.TableDefs(TableCount).RefreshLink End If
Next TableCount
The entire process takes perhaps 5-10 seconds when I am the only user
connected to the DB. If, however, any other user is already connected when I
get to this point, the process takes perhaps five minutes. If I have the
other user get out of the app while this is running, it seems to release
something, and the re-link finishes almost immediately.
Ideas?
BE: MDB on Win2003 server
The path to the BE on my test system is different than the path to the BE
for the live users. When I distribute a new MDE, I trap an error on the first
attempt to contact the BE, and then re-link automatically. Here is the code,
in brief (omitting the dimensioning of some variables, etc.)
Set dbProgram = CurrentDb
For TableCount = 0 To dbProgram.TableDefs.Count - 1
If dbProgram.TableDefs(TableCount).Connect <> "" Then
dbProgram.TableDefs(TableCount).Connect = ";DATABASE=" &
FilePathData & ""
dbProgram.TableDefs(TableCount).RefreshLink End If
Next TableCount
The entire process takes perhaps 5-10 seconds when I am the only user
connected to the DB. If, however, any other user is already connected when I
get to this point, the process takes perhaps five minutes. If I have the
other user get out of the app while this is running, it seems to release
something, and the re-link finishes almost immediately.
Ideas?