Is There A Limt On Forms In A MDB?

[Guest]

Access 2K

I am creating and updating forms that are on a termial server

I have started to get very slow respone times when saving my edits.
sometimes I have to close down the app and lose all my edits its so slow. 2-5
minutes or better.

Any ideas on what might be happening? This still happens ever after a
sucessful comple, compact and repair of the mdb.

I have admin rights on the TS box.

Any help would be appreciated.

 

[MacDermott]

Do you have all of the service packs installed on A2K?
The behavior you describe is reminiscent of early versions of A2K.
They had a lot of other problems, too -
I'd strongly advise applying the service packs if you haven't yet.

HTH

 

['69 Camaro]

Hi.

There isn't a specific limit on forms per se, but the maximum number of
objects an Access 2K database can hold is 32,768. The maximum number of
modules is 1,000, and many forms have modules, so that may a reachable
limit. But you probably aren't running into either of these limits.

Any ideas on what might be happening?

Yes. You are editing objects which will all be saved in the same monolithic
record, no matter how many of them were never changed. The more objects in
the database, the longer it takes to save all of them.

You are also making design changes from across the network. Heavy network
traffic adds to the time it takes to save the monolithic record. Is your
database split? If it were, you could make design changes to objects in a
database file on your own computer, then when you are finished, you could
copy your development version over to the production version without
overwriting any of the data. For more information on the benefits of a
split database, please see the following Web page:

http://www.Access.QBuilt.com/html/gem_tips.html#SplitDB

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)

 

[Guest]

Thanks for your reply.

Using Access 2000 9.0.6926 SP3 which I think is uptodate but not really sure

Again thanks

 

[Guest]

Thanks for your reply.

Data Base is Spit. Front End is about 13 Megs. All data is presently on
the server I have no local data to work with. Max 3 users on the TS at any
one time. I have a 756K Up 3 Meg down connection and everything works great
but the saving of the forms.???

Using Access 2000 9.0.6926 SP3 which I think is uptodate but not really
sure. I'll try ziping it us and sending it to my local desktop but it was
working fine just a day or so ago. I have good antivirus and spyware
software loaded and up to date.

Strange

Again thanks

 

['69 Camaro]

Hi.

Data Base is Spit. Front End is about 13 Megs.

13 MB is on the heavy side for a front end. Do you have graphic images in
these forms? That would help explain the size.

Max 3 users on the TS at any
one time.

The users each have a copy of the front end in their own directory on the
Terminal Server, or is everybody sharing one copy of the front end?

Using Access 2000 9.0.6926 SP3 which I think is uptodate but not really
sure.

SP-3 is the latest for Access 2K. Jet 4.0 needs SP-8 and MDAC 2.8 needs
SP-1 to be up to date. Make sure that every computer connecting to the
Access databases is using the same versions of these service packs.

but it was
working fine just a day or so ago.

Make a copy of the front end and open it using the /decompile command-line
switch, then compile the code again when it's finished. Then you can use
this copy to test on the Terminal Server to see whether it's still slow when
you save your changes to the forms. If it's as fast as it used to be, then
you've fixed the problem, and just need to rename the copy to the original
after backing up, then deleting the original.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)