Memory and corruption issues

  • Thread starter Thread starter Mietzsch
  • Start date Start date
M

Mietzsch

I have developed an Access 97 Application. I am running
into memory errors and a corruption issue when there are
about 5 - 10 users.
The only thing I can think of so far is, I make use of
several dropdowns and subforms. I may have done it to
excess. The size of the front-end is 3 megs, with the
potential for a lot more. There are many tables, queries,
forms, and reports.

Can anyone make any suggestions, as to what I should look
at and if I am going in the right direction. And if so,
how can I correct this problem?

Any help would be most appreciated.
 
The specs you are describing seem pretty low, access
should easily be able to handle. Make sure the virtual
paging memory is set high enough on each client pc. Also,
make sure the "server" pc has plenty of RAM (512mb.)
But 10 users should not be a problem. I would also
upgrade to access 2000 at least. As far as the curruption
issue goes, you need to ensure your network integrity is
solid. Also, power dips and spikes can reak havok on an
access database and cause curruption to the backend. Use
low-end UPS units on each workstation ($40 each). See
knowledge base article 209137 and 300216
 
The problem you describe is typically caused by Windows
or by your hardware, not by Access or your Application.

My 8MB A97 single file Front End and my multiple file 40MB
Front End don't have any memory problems on Win98 or Win2K
or WinXP.

I don't have more than a couple of forms (with two subforms
and a half-dozen drop-downs each) open at once, but if you
leave all the forms open you should get an error message,
not corruption, and it should be independent of the
number of users.

Make sure that Office 97 is patched to SP2, Jet 3.5 is
patched to SR3, and Windows is patched to the latest
release. (There have been bugs in the Windows Network
code that caused file corruption on shared files.)

Replace your FE and BE with clean, uncorrupted copies.
(Restore your FE from backup if possible: if not, decompile
and import to a new database).

The only regular form of corruption I have had with A97
was Memo field corruption (fixed in SP2/SR3). There were
also some Bookmark bugs which I never experienced, and the
relationship bug, which you would probably never notice.

We did see problems on early versions of Win2K, and there
have always been occasional reports of problems caused by
Network Faults and Power Faults.

(david)
 
Even in the final release of Office 2000, A97 was
more stable than A2K. If file corruption is a problem,
do not upgrade from A97 until the file corruption
problem has been fixed.

(david)
 
Mietzsch said:
I have developed an Access 97 Application. I am running
into memory errors and a corruption issue when there are
about 5 - 10 users.
Click to expand...

What kind of memory errors? And corruptions? What are the exact
messages.
The only thing I can think of so far is, I make use of
several dropdowns and subforms. I may have done it to
excess.
Click to expand...

Very unlikely. I have one form with 12 tabs, 20 or 30 combo boxes aka
dropdowns and 10 or more subforms. And lots of code in behind the
form.
The size of the front-end is 3 megs, with the
potential for a lot more. There are many tables, queries,
forms, and reports.
Click to expand...

Still quite small. The above FE is about 20 or so MB in size.
Can anyone make any suggestions, as to what I should look
at and if I am going in the right direction. And if so,
how can I correct this problem?
Click to expand...

I'd start by reviewing the Access Corruptions FAQ at my website to see
if your symptoms match.

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
 
Back
Top