Network access - table locks up

[Noni Ledford]

Hi - I have a database on a network, and each user logins using a
shortcut from his PC to the shared database. There is a table created by
a make-table query that locks up whenever more than one user is in the
database. It doesn't matter that the users open completely different
clients, forms, etc, as long as there are more than one user opens the
database this table locks up. And the function that recalculates the
amount doesn't work.

Any idea how to solve this problem? I would appreciate it very much.

Noni

[Cheryl Fischer]

Noni,

Problems such as the ones you describe usually clear up as if by magic when
the database is split into a Front-End and a Back-End.

The Front-End contains all Queries, Forms, Reports, Macros, Modules and
local-use tables. The Front-End contains links to the tables in the
Back-End, which contains only Tables containing data which is to be shared.
Each Front-End is then distributed to and run from each user's hard drive.
--

Cheryl Fischer, MVP Microsoft Access
Law/Sys Associates, Houston, TX
"Noni Ledford" <NO********@NOstretchSPAMphotography.com> wrote in message
news:NO******************************@news03.east. earthlink.net...

Hi - I have a database on a network, and each user logins using a
shortcut from his PC to the shared database. There is a table created by
a make-table query that locks up whenever more than one user is in the
database. It doesn't matter that the users open completely different
clients, forms, etc, as long as there are more than one user opens the
database this table locks up. And the function that recalculates the
amount doesn't work.

Any idea how to solve this problem? I would appreciate it very much.

Noni

[Noni Ledford]

In article <#5*************@TK2MSFTNGP10.phx.gbl>,
"Cheryl Fischer" <ch***********@NOSPAMmsn.com> wrote:

Noni,

Problems such as the ones you describe usually clear up as if by magic when
the database is split into a Front-End and a Back-End.

The Front-End contains all Queries, Forms, Reports, Macros, Modules and
local-use tables. The Front-End contains links to the tables in the
Back-End, which contains only Tables containing data which is to be shared.
Each Front-End is then distributed to and run from each user's hard drive.
--

Cheryl Fischer, MVP Microsoft Access
Law/Sys Associates, Houston, TX
"Noni Ledford" <NO********@NOstretchSPAMphotography.com> wrote in message
news:NO******************************@news03.east. earthlink.net...

Hi - I have a database on a network, and each user logins using a
shortcut from his PC to the shared database. There is a table created by
a make-table query that locks up whenever more than one user is in the
database. It doesn't matter that the users open completely different
clients, forms, etc, as long as there are more than one user opens the
database this table locks up. And the function that recalculates the
amount doesn't work.

Any idea how to solve this problem? I would appreciate it very much.

Noni

Thanks Cheryl. I appreciate yor suggestion. This database doesn't have
any local-use tables, all the tables are shared. Would it be a good
idea if I split the database Front-End: Queries, Forms, Reports, Macros,
Modules, and Back-End: all tables? Or is there any other way to split
it?

Thanks so much,
Noni Ledford

[Cheryl Fischer]

The split of your database as I described it earlier would be considered the
"best practice", although I think there might be some room for exceptions.
I have not myself seen such an exception, but it's possible.

I wonder about your Make-Table query. What is its purpose?

--

Cheryl Fischer, MVP Microsoft Access
Law/Sys Associates, Houston, TX
"Noni Ledford" <NO********@NOstretchSPAMphotography.com> wrote in message
news:NO******************************@news03.east. earthlink.net...

In article <#5*************@TK2MSFTNGP10.phx.gbl>,
"Cheryl Fischer" <ch***********@NOSPAMmsn.com> wrote:

Noni,

Problems such as the ones you describe usually clear up as if by magic when the database is split into a Front-End and a Back-End.

The Front-End contains all Queries, Forms, Reports, Macros, Modules and
local-use tables. The Front-End contains links to the tables in the
Back-End, which contains only Tables containing data which is to be shared. Each Front-End is then distributed to and run from each user's hard drive.

--

Cheryl Fischer, MVP Microsoft Access
Law/Sys Associates, Houston, TX
"Noni Ledford" <NO********@NOstretchSPAMphotography.com> wrote in message news:NO******************************@news03.east. earthlink.net...

Hi - I have a database on a network, and each user logins using a
shortcut from his PC to the shared database. There is a table created by a make-table query that locks up whenever more than one user is in the
database. It doesn't matter that the users open completely different
clients, forms, etc, as long as there are more than one user opens the
database this table locks up. And the function that recalculates the
amount doesn't work.

Any idea how to solve this problem? I would appreciate it very much.

Noni

Thanks Cheryl. I appreciate yor suggestion. This database doesn't have
any local-use tables, all the tables are shared. Would it be a good
idea if I split the database Front-End: Queries, Forms, Reports, Macros,
Modules, and Back-End: all tables? Or is there any other way to split
it?

Thanks so much,
Noni Ledford

[Tony Toews]

Noni Ledford <NO********@NOstretchSPAMphotography.com> wrote:

Hi - I have a database on a network, and each user logins using a
shortcut from his PC to the shared database. There is a table created by
a make-table query that locks up whenever more than one user is in the
database. It doesn't matter that the users open completely different
clients, forms, etc, as long as there are more than one user opens the
database this table locks up. And the function that recalculates the
amount doesn't work.

1) I'd agree with Cheryl. Split your MDB.

See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp.htm for more info. See
the Auto FE Updater downloads page
http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless.. It also supports Terminal Server/Citrix quite nicely.

2) I'd suggest you create a temporary MDB and store the table created
by your make table query in there instead.

See the TempTables.MDB page at my website which illustrates how to use
a temporary MDB in your app.
http://www.granite.ab.ca/access/temptables.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

[Noni Ledford]

Tony and Cheryl, thanks so muh for your suggestions. I've been reading
more about database split from your links, and finding more information
about it. It makes sense. I appreciate your expertise. Once I split
the database I may ask you other questions. Thanks again.

Noni

In article <kt********************************@4ax.com>,
Tony Toews <tt****@telusplanet.net> wrote:

Noni Ledford <NO********@NOstretchSPAMphotography.com> wrote:

Hi - I have a database on a network, and each user logins using a
shortcut from his PC to the shared database. There is a table created by
a make-table query that locks up whenever more than one user is in the
database. It doesn't matter that the users open completely different
clients, forms, etc, as long as there are more than one user opens the
database this table locks up. And the function that recalculates the
amount doesn't work.

1) I'd agree with Cheryl. Split your MDB.

See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp.htm for more info. See
the Auto FE Updater downloads page
http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless.. It also supports Terminal Server/Citrix quite nicely.

2) I'd suggest you create a temporary MDB and store the table created
by your make table query in there instead.

See the TempTables.MDB page at my website which illustrates how to use
a temporary MDB in your app.
http://www.granite.ab.ca/access/temptables.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

[Tony Toews]

Noni Ledford <NO********@NOstretchSPAMphotography.com> wrote:

Tony and Cheryl, thanks so muh for your suggestions. I've been reading
more about database split from your links, and finding more information
about it. It makes sense. I appreciate your expertise.
You're quite welcome.
Once I split
the database I may ask you other questions.

Please ask. That's what we're here for.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

[Ed]

I have a similar problem. I am using a billing program (Office
Therapy) that is based on Access and intermittently it locks up and
will not let the server enter numbers. Others on the network
accessing the server have no problems. The program will take one
letter, then writes over that letter, indicating only one field is
available, but it will not take any numbers. No error message is
generated. I know nothing about Access and am at a loss as to what to
try and the program no longer provides technical support. Any help
would be appreciated.
Thanks,
Ed

[Tony Toews]

ea****@aol.com (Ed) wrote:

I have a similar problem. I am using a billing program (Office
Therapy) that is based on Access and intermittently it locks up and
will not let the server enter numbers. Others on the network
accessing the server have no problems. The program will take one
letter, then writes over that letter, indicating only one field is
available, but it will not take any numbers.

Ah, so Access only allows you to enter one character into that field. You enter
another one and it overwrites that character?

That is wierd. Let us think on that one for a bit.

Tony

--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm