Temporary Tables. Where will they be created

[Mike Ridley]

I have 2 databases called (for example) "progs.mdb" and "files.mdb".
Both these databases reside on computer "myserver". The progs database
has links to the tables in the files database.
"myclient1" runs a shortcut "msaccess.exe \\myserver\progs.mdb /x
startmacro".
"myclient2" runs his shortcut "msaccess.exe \\myserver\progs.mdb /x
startmacro".

If I use a temporary table I take it that it will be created on
"myserver" in the "progs.mdb" and if the two users try to create the
table at the same time I'm going to have big problems.

I need to create the temporary tables on the clients machine but still
retain a central progs database.

Thanks Mike

[Larry Linson]

Actually, you are raising the probability of corruption if you have multiple
users logging in to the same front-end or monolithic database. You need to
give each user a copy of the front-end and link to the shared tables
database.

Where temporary tables are created depends on how you go about creating
them, but normally, they are in the database that the user is executing
(front-end). However, there is a method for creating a temporary database
and creating temporary tables in that, then deleting the temporary database
when done to avoid memory bloat. You'll find it at MVP Tony Toews' site,
http://www.granite.ab.ca/accsmstr.htm.

He's also got the best collection of information and links on multiuser
Access environments that I know about, so it'd be a good place to go and
explore.

Larry Linson
Microsoft Access MVP

"Mike Ridley" <gi******@hotmail.com> wrote in message
news:e5*************************@posting.google.co m...

I have 2 databases called (for example) "progs.mdb" and "files.mdb".
Both these databases reside on computer "myserver". The progs database
has links to the tables in the files database.
"myclient1" runs a shortcut "msaccess.exe \\myserver\progs.mdb /x
startmacro".
"myclient2" runs his shortcut "msaccess.exe \\myserver\progs.mdb /x
startmacro".

If I use a temporary table I take it that it will be created on
"myserver" in the "progs.mdb" and if the two users try to create the
table at the same time I'm going to have big problems.

I need to create the temporary tables on the clients machine but still
retain a central progs database.

Thanks Mike

[Mike Ridley]

Thanks for the information. I found Tony's site very helpful.
Calling the front end "progs.mdb" from the server saves me having to
maintain separate copies on the client PCs.

"Larry Linson" <bo*****@localhost.not> wrote in message news:<lX*****************@nwrddc03.gnilink.net>...

Actually, you are raising the probability of corruption if you have multiple
users logging in to the same front-end or monolithic database. You need to
give each user a copy of the front-end and link to the shared tables
database.

Where temporary tables are created depends on how you go about creating
them, but normally, they are in the database that the user is executing
(front-end). However, there is a method for creating a temporary database
and creating temporary tables in that, then deleting the temporary database
when done to avoid memory bloat. You'll find it at MVP Tony Toews' site,
http://www.granite.ab.ca/accsmstr.htm.

He's also got the best collection of information and links on multiuser
Access environments that I know about, so it'd be a good place to go and
explore.

Larry Linson
Microsoft Access MVP

"Mike Ridley" <gi******@hotmail.com> wrote in message
news:e5*************************@posting.google.co m...

I have 2 databases called (for example) "progs.mdb" and "files.mdb".
Both these databases reside on computer "myserver". The progs database
has links to the tables in the files database.
"myclient1" runs a shortcut "msaccess.exe \\myserver\progs.mdb /x
startmacro".
"myclient2" runs his shortcut "msaccess.exe \\myserver\progs.mdb /x
startmacro".

If I use a temporary table I take it that it will be created on
"myserver" in the "progs.mdb" and if the two users try to create the
table at the same time I'm going to have big problems.

I need to create the temporary tables on the clients machine but still
retain a central progs database.

Thanks Mike

[David W. Fenton]

gi******@hotmail.com (Mike Ridley) wrote in
news:e5**************************@posting.google.c om:

Calling the front end "progs.mdb" from the server saves me having
to maintain separate copies on the client PCs

And is absolutely the wrong thing to do, as eventually, it will blow
up in your face for any number of reasons. You may be lucky and only
corrupt the front end. Or you may corrupt the back end data file, as
well.

Users of a shared front end can also experience weird behavior, not
limited to getting write conflict dialogs when they close forms (for
example, if they've applied a filter/sort, the default is to save
that on close of the form, and if someone else has done the same
thing, there could be a write conflict between the two people
closing the form).

And, of course, from A2K on, you can't actually make changes in the
front end while users are in it, so that "advantage" (I would have
called it "disaster waiting to happen") is gone.

It was never a good idea.

The Access documentation has never suggested such a multi-user setup
for as long as I've been using it (since 1996, with Access 2.0). I
don't understand how anyone who has a multi-user app could end up
with the impression that it's a good idea.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc