[dba-Tech] Another database from hell

Hi Mark:

I have that same problem on one of my systems. Access connection keeps
dropping for no apparent reason. (We have blamed the new system's method of
auto saving the desktop and local data at various intervals through out the
day as the most likely root cause.)

The program moves the FE's to each station via automation, upon start and
the issues continued. I have told the client that I could move the BE to a
MS SQL 2008 express server on a Server2008 and make all the FE connections
unbound. That is no simple feat but the client is concerned about the
cost...it will be a lot of work. 

OTOH I am sure that would solve the problem.  

Moving the whole FE and BE to DNN is likely to cost yet more.

Of course the ultimate solution is to build an intranet application in
ASP.Net with a MS SQL BE. Then the issue of an old machines becomes
irrelevant and the client can popup as many browsers windows as the local
resources will allow.

HTH
Jim

-----Original Message-----
From: dba-tech-bounces at databaseadvisors.com
[mailto:dba-tech-bounces at databaseadvisors.com] On Behalf Of Mark Breen
Sent: Saturday, January 07, 2012 10:32 AM
To: Access Developers discussion and problem solving; Discussion of Hardware
and Software issues
Subject: [dba-Tech] Another database from hell

Hello AccessD Friends,

I have a new client and my task is to replace an aging Access database with
a DotNetNuke based system.

Because the Access db is due for early retirement, neither I nor the client
wish to invest any time or effort in re-programming.  I am prepared to
perform some minor improvements, but on the basis that it is working as is
for a number of years, I do not want to do too much work on it.

The reason I am seeking help from AccessD is that the Access App is loosing
connection with the network a few times per day.  The message the users get
is

*"Your network access was interrupted.  To continue, close the database and
then open it again.    You cannot save the record at this time"*

Now the scary bit,
1) the db is 120 MB when fully compacted but quickly grows back to 300MB.
2) There are 12 to 15 simultaneous users.
3) Each user always opens two instances of MS Access so that they can keep
two different screens open at all times.
4) It does not help if I configure a BE and an FE or simply include all
tables in the one mdb file.
5) They do not currently operate with an FE on the local machine (I am
considering moving FE's locally to test that).
6) All PCs are slow and old
7) Error handling and best practices are absolutely non-existent
8) Some PCs run Access 2007 and some run 2003.

The db files are stored on a Windows 2008 R2 Server, but the users think
they had better performance when it was hosted on Windows XP machines, I am
not sure if that is correct but can check.

Any suggestions ??

My advice to someone in my position would be to simply not touch the Access
App and focus on the new app, but if I could think of a quick win, I would
try it to simply prevent the error mentioned above.

Thanks for any advice and I will understand if you have non at all :)

Mark
_______________________________________________
dba-Tech mailing list
dba-Tech at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-tech
Website: http://www.databaseadvisors.com