Relinking problem

[cmd]

I use the following code (behind a command button on the FE) to relink
from a user's local copy of the BE to the file-server's BE on our LAN.
I use this, for example, when a person brings in their laptop and
connects to our LAN.

The code works fine if there are no other users accessing the server's
BE at the time. If the file-server's BE is open at the time, however,
then the relinking process does not finish -- it just pauses. When
everyone else closes out of the database, then the process continues on
its own and the laptop's FE is now linked to the server's BE.

Our multi-user, split database setup works fine normally --
simultaneous users can open and close out of the database without a
problem -- as long as their FEs are already linked to the server's BE.

One other factor: The FEs have a hidden form, always open, and which is
based on a utility table in the BE.

Question:
Is there anything I can do which will allow computers on our LAN to
relink from a local BE to the server's BE without having everyone else
close out of the database?

Thanks for any help.
Mark

Dim dbs As Database
Dim tdf As TableDef
Dim Tdfs As TableDefs
Dim NewPathname As String
Set dbs = CurrentDb
Set Tdfs = dbs.TableDefs

'************** **Link to Network Drive-P

If Len(Dir("P:\fps data.mdb")) = 0 Then
MsgBox "You're not connected to the network."
Resume exithandler
End If

NewPathname = "P:\fpsdata.mdb "

'Loop through the tables collection
For Each tdf In Tdfs
On Error GoTo errhandler

'...link main tables
If Len(tdf.Connect ) > 0 Then
tdf.Connect = ";DATABASE= " & NewPathname
tdf.RefreshLink
End If
Next 'Goto next table

[paii, Ron]

<cm*@mountain.n et> wrote in message
news:11******** **************@ g44g2000cwa.goo glegroups.com.. .

Thank you, Ron.
I'll give that a try, but I think your initial caution about not being
able to re-attach to open tables is correct, and even though it
appeared I was doing just that, the database was probably just
confirming the links as they had already existed -- and, therefore, not
hanging up, or producing an error of some kind.

Mark

The caution of open tables was only for tables opened by the FE database
doing the re-attached. You should be able to attach to the BE while other
users have it open, unless someone has it open exclusively.

[David W. Fenton]

"paii, Ron" <pa**@packairin c.com> wrote in
news:Fe******** ************@at henet.net:

You cannot reattach a table that is open. Close all forms and
processes with open tables before reattaching. You should also
close and reopen the FE database after reattaching the tables.

On this latter point, why? I've never done so, ever -- not even once
-- and my computer, nor any computer belonging to my clients, has
ever exploded or anything.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[David W. Fenton]

"paii, Ron" <pa**@packairin c.com> wrote in
news:go******** ************@at henet.net:

Here is a snippet of the code I have been using since 94.
Some of it came from Solutions.MDB which was part of Access 2
This code deletes the table attachment then creates a new
attachment. This may or may not be the problem, but it works from
me.

CurDB.TableDefs .Delete "Table Name"
Set CurTable = CurDB.CreateTab leDef("TableNam e")
CurTable.Connec t = ";DATABASE= " & filename

CurTable.Source TableName = "Table Name"
CurDB.TableDefs .Append CurTable

CurTable.Refres hLink

This can be orders of magnitude slower than updating the connect
string. It isn't in all cases, but I've seen it take *MUCH* longer
than the former.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[cmd]

Ron,

Are you saying that as long as the FE first closes all of its open
tables, then it should be able to attach to the BE's tables on the
server regardless of whether anyone else is in the database (provided
they haven't opened it exclusively)?

If that's what you're saying, then I guess when my FE is already
attached to the BE on the server and I click the re-attach button --
which first closes the hidden form -- then the FE does in fact
re-attache to all the tables in the server's BE.

But, why would the same process "hang" until other users have exited
the database in the case where my FE was initially linked to my local
BE? The hidden form is still closed first before trying to attach to
the server's BE.

Mark

[paii, Ron]

"David W. Fenton" <XX*******@dfen ton.com.invalid > wrote in message
news:Xn******** *************** ***********@127 .0.0.1...

"paii, Ron" <pa**@packairin c.com> wrote in
news:Fe******** ************@at henet.net:

You cannot reattach a table that is open. Close all forms and
processes with open tables before reattaching. You should also
close and reopen the FE database after reattaching the tables.

On this latter point, why? I've never done so, ever -- not even once
-- and my computer, nor any computer belonging to my clients, has
ever exploded or anything.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

My reason goes back to the original code and Access 2, which behaved
strangely if I didn't reopen the FE. It has works in my environment so I
haven't changed the procedure. Also my applications get startup data from
the BE, without the restart I would need to call a function to reinitialize
the app.

I use re-attach to change to a different BE, normally to attach my
developmental FE to the production BE before distributing it to the users.

[paii, Ron]

<cm*@mountain.n et> wrote in message
news:11******** **************@ g43g2000cwa.goo glegroups.com.. .

Ron,

Are you saying that as long as the FE first closes all of its open
tables, then it should be able to attach to the BE's tables on the
server regardless of whether anyone else is in the database (provided
they haven't opened it exclusively)?

If that's what you're saying, then I guess when my FE is already
attached to the BE on the server and I click the re-attach button --
which first closes the hidden form -- then the FE does in fact
re-attache to all the tables in the server's BE.

But, why would the same process "hang" until other users have exited
the database in the case where my FE was initially linked to my local
BE? The hidden form is still closed first before trying to attach to
the server's BE.

Mark

I just re-attached to a BE opened and by 4 or 5 users, so the process works.
All I can suggest is to do a compact and repair on the BE. Also add some
code to your re-attach function to output each table name before you attempt
to refresh. Is it the same table hanging? If so, verify the table is ok and
that your users FE doesn't lock the table at some point..

[cmd]

Ron,

When you re-attached to the BE, had your FE already been attached to
that same BE? My problem only occurs if my FE is initially attached to
C:\Access97 (a laptop's BE brought from home, for example) and I then
try to attach to P:\Access97, i.e., the server's BE. ("Access97" is
just the name of the folder where I place local and server BEs).

To clarify ... I'm just using the word "hang" the same as I would the
word "pause". There does not seem to be any error generated. My "Please
Wait" pop-up form just sits there until any other users close out of
the database. As soon as they do, the pop-up form closes and the tables
have been attached to the server's BE.

Mark

[paii, Ron]

<cm*@mountain.n et> wrote in message
news:11******** **************@ g49g2000cwa.goo glegroups.com.. .

Ron,

When you re-attached to the BE, had your FE already been attached to
that same BE? My problem only occurs if my FE is initially attached to
Normally I am changing from a local Test copy of the BE, to the shared copy
on a server.
C:\Access97 (a laptop's BE brought from home, for example) and I then
try to attach to P:\Access97, i.e., the server's BE. ("Access97" is
just the name of the folder where I place local and server BEs).

To clarify ... I'm just using the word "hang" the same as I would the
word "pause". There does not seem to be any error generated. My "Please
Wait" pop-up form just sits there until any other users close out of
the database. As soon as they do, the pop-up form closes and the tables
have been attached to the server's BE.

Mark

[cmd]

Normally I am changing from a local Test copy of the BE, to the shared
copy
on a server.

--That sounds just like what I'm doing.

If an error was being produced, I could probably identify what was
happening. But, since the process is only pausing, I'm not sure how I
would identify any particular table that might be stopping the process
until other users log out. Furthermore, it's the same FE that has no
problems re-attaching even with other users in the database -- provided
that the FE started out as attached to P:\Access97. The BE on my local
drive is also the same as the BE on the server -- I frequently copy it
from the server to my development computer.

[paii, Ron]

<cm*@mountain.n et> wrote in message
news:11******** **************@ g47g2000cwa.goo glegroups.com.. .

Normally I am changing from a local Test copy of the BE, to the shared
copy
on a server.

--That sounds just like what I'm doing.

If an error was being produced, I could probably identify what was
happening. But, since the process is only pausing, I'm not sure how I
would identify any particular table that might be stopping the process
until other users log out.
from your code

If Len(tdf.Connect ) > 0 Then

' I am guessing you can get the table name like this. Otherwise check Access
help.
msgbox tdf.Name

tdf.Connect = ";DATABASE= " & NewPathname
tdf.RefreshLink
End If
Furthermore, it's the same FE that has no problems re-attaching even with other users in the database -- provided
that the FE started out as attached to P:\Access97. The BE on my local
drive is also the same as the BE on the server -- I frequently copy it
from the server to my development computer.

By the way I am also using Access97.

Also check that you have the sr2b service pack installed.