database stability

[strucker]

Hello

At work we have this database that was converted to Access97 to Access2K. For five years prior to conversion of the database there were very few problems at all. After converting it we are constantly compacting and repairing it to fix any errors and sometimes that doesn't work and I end up having to get backup tapes and loosing information. It would be a pain to recreate the database in 2000, but wouldn't it be better to use SQL???? More stable??? slightly faster??? Better backup system??? I don't know SQL very well at all, would upsizing be more trouble for me than recreating the database in 2000???? Thanks!!

Nolan

 

[Nowell]

Hi there

I had this exact same problem when upgrading from 97 to xp and I tried so many different things to fix the problem, and the only solution was to upgrade to SQL server.
I even went to microsoft technical support for help and they could not fix the problem.

How many concurrent users do you have?
Do you have the database split?
How often are concurrent users actually apending records?

How that I have SQL server, I have over 75 users all using the system at the same time and it works like a dream.

 

[strucker]

Thanks for the reply!

I only have ten or so users and the database is in constant use by most of the users and is appended very frequently throught the day. The information in this database has to be available to the users 24/7 so that they can report to customers and bosses. The database is not split. Splitting may prevent a few errors, but I want a rock solid application that I can create and let fly, not just fix less. How dificult is it to create tables on SQL and then link them to Access??? I hear project is a pain.

Thanks for your help?

 

[Nowell]

Hi, if you only have ten users in theory you should be ok, one of the main reasons for database corruption is dropping network connections.
How stable is your network?
Are your users not shutting down the system properly?

I would strongly advise splitting the database asap, it will help you more than you think. With a split database you are only sending raw data over the network, the way you currently have it means you have to send all the forms, reports and graphics over the network to each user causign big network traffic.

How are your tables organised? are they normalised? If you have more than thirty fields in a table that is being currently updated then you could be looking at trouble espeically if you have large text fields.

You could leave the back end in 97 and use 2000 front ends for your users, this works good, I have tried it.

Man this has become a complete essay.

Cheers

Nowell