Re: Access database stability problems

So far, our data file is still in tact. One time I noticed a contact's info was garbled up, but luckily it wasn't anything important.

I know that moving to SQL would be a good long-term idea, but I just don't have the know-how or resources to do it right now.

Let me pose something else that may or may not help. Some of our computers are running an access database that is similar to mine. Consider it the long-lost cousin that branched off from mine several years ago. The backend data files are even located on the same network drive on the server. I found out today that people running that database are NOT having crashes like we are. Odd, isn't it!? If it were a hardware or NIC driver issue, wouldn't they be having the same problem?

Could there be something I'm overlooking? I was almost convinced that this was an OS or hardware-related issue, but maybe I'm wrong. Maybe this is somehow specific to my database files only. I just don't have a clue what would be causing it though. Sorry... I'm thinking out loud here hoping someone might have an idea.

Todd


"Joe" <joe@xxxxxxxxxxxxxx> wrote in message news:%23RUBMQEIKHA.2516@xxxxxxxxxxxxxxxxxxxxxxx
Todd wrote:
Thank you, Ace. I wasn't familiar with the other newsgroup. Much appreciated!!!


"Todd" <Todd@xxxxxxxxxxxxxxx> wrote in message news:AF31867F-90BD-4C7B-8B80-D9C493F24627@xxxxxxxxxxxxxxxx
We recently upgraded from SBS 2003 to SBS 2008. For some reason, our Microsoft Access database is crashing since the change. Our database has 3 users... we all have the client app part on our individual computers and the data is located on the server via a mapped network drive. It seems that we are occassionally losing network connectivity.

There isn't really a consistency to the issue. One computer may lose the connection and the database crashes while the other two remain unaffected. Every computer, however, is experiencing the problem 2 or 3 times per day.

We are using the same computer as before and the same network cable. The only difference (albeit a big one) was the upgrade to SBS 2008. Any ideas or suggestions? Thanks in advance!!!


OK, you obviously have some kind of network problem, and it seems unlikely that the OS being SBS2008 is the fundamental cause. Best of luck, intermittent faults are not fun. My guess is that you start with NIC drivers.

What I wanted to strongly recommend is moving your database to an SQL server of some kind, SQL Server 2005 Express if nothing else. I would assume that there is a Microsoft utility for migrating the data, I'm not a user of SQL Server, but I've moved quite a few Access backends to an alternative SQL server.

Not only do you see a dramatic speed improvement, but it's practically impossible to damage the database. You haven't said whether 'crashing the database' is just a matter of Access losing its network connection and screaming blue murder, or whether it's actually breaking the backend data file. If the latter has not happened yet, you've been extremely lucky, and you need to be making very frequent backups.

--
Joe

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4348 (20090819) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com





__________ Information from ESET NOD32 Antivirus, version of virus signature database 4348 (20090819) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com



.

Relevant Pages

  • Re: DTS Performance
    ... Make sure the log and data file size are not going to need to expand during the import ... Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) ... www.SQLDTS.com - The site for all your DTS needs. ... > this database is 2.74 GB and the database itself is 2.67 GB. ...
    (microsoft.public.sqlserver.dts)
  • Re: SHRINKDATABASE question
    ... should leave your database at 50 MB ... Wayne Snyder, MCDBA, SQL Server MVP ... When you specify target percentage of 20 % for shrinking your ... > data file and then shrinks the file. ...
    (microsoft.public.sqlserver.server)
  • separating sql server data files
    ... i was just reading about separating database files to improve sql server ... we are running sql server 2000. ... data file and one log file. ...
    (microsoft.public.sqlserver.setup)
  • Re: SQL Database Has Overstayed its Welcome
    ... You can change the default data file location by using SSMS easily. ... However, if you attach *.mdf file to SQL Server, the data file stays where it was after attaching. ... I am not sure what you did, but if the *.mdf file cannot be deleted/copied, then the data file must belong to an existing database and still in use. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Relink tables questions
    ... For example, the network is down, a network admin changed ... circumstances that would make relinking necessary. ... present users with a dialog for selecting the correct database file. ... If your code returns an error, you know that the data file is not ...
    (microsoft.public.access.formscoding)
Loading