Please help - SERIOUS issues

[denileigh]

Hello all,

I have a database with a front end and back end (tables on the server) that was recently converted from Access 2003 to Access 2010.

For some reason the back end keeps hanging and I have to constantly compact and repair and there has been major data loss on a regular basis.

Can anyone give me any hints as to what might possibly be going on with this and how to solve it?

Thanks so much,
Dianne

 

[shadow9449]

Dianne:

My first two questions:

- Is the network hardwired or wireless?
- You said that the backend is on the server. What about the frontend? Does each user have his/her own version on the local computer or is there one copy that everyone shares?

SHADOW

 

[denileigh]

Yes, that is exactly how it's set up! We are in a world of hurt too....we keep entering stuff, running reports, etc. and the next day. The data is gone! That and it's locking up non-stop...have to compact and repair at a minimum of 10x a day! Any ideas?

 

[jdraw]

Is this your production db?
Did you have any issues during testing/development/conversion?
Other than convert from 2003 to 2010 have you changed anything else?
Server; more users; new tables/queries;temp tables; processes????

 

[denileigh]

And it's hardwired....the connection bleeps alot though.

 

[bob fitz]

Yes, that is exactly how it's set up!

I'm sorry, but that doesn't really answer the questions that shadow9449 asked.
Is the network hardwired or wireless?
How many front ends are there. Is there a front end on each users machine?

 

[MSAccessRookie]

Dianne:

My first two questions:

- Is the network hardwired or wireless?
- You said that the backend is on the server. What about the frontend? Does each user have his/her own version on the local computer or is there one copy that everyone shares?

SHADOW

Yes, that is exactly how it's set up! We are in a world of hurt too....we keep entering stuff, running reports, etc. and the next day. The data is gone! That and it's locking up non-stop...have to compact and repair at a minimum of 10x a day! Any ideas?

Shadow provided two choices and your answer was "that is exactly how it's set up". We can make assumptions, and I am sure that are all hoping it is choice #1, but it is better to hear from you. Which one is it (Choose one)?

1. Each user has his/her own version on a local computer
2. There one copy that everyone shares

Assuming that it is choice #1, you might want to verify that all users are following the same procedure, and that none of them are sharing a common Front End.

ADDITIONAL THOUGHT:

By your descrtiption, I presume that your Back End is now using MS Access 2010. Do all of your users have Front Ends that are Access 2010 as well? If any of them are using MS Access 2003, or MS Access 2007, let us know that as well.

 

[boblarson]

Yes, front ends should NOT be from a lower version than the backend.

 

[denileigh]

I'm sorry. Here you go.

Each user has his/her own version on a local computer
Front end is 2010.
The back end (all the tables) are on the server and shared.
Network/server is hardwired.

Thanks so much!

 

[boblarson]

All users have read, write, delete rights to the folder where the backend is located?

Also, your server doesn't happen to have Novell as its Operating System, does it?

 

[GinaWhipp]

And let's check those References...

http://www.access-diva.com/d5.html

...especially, http://www.access-diva.com/d5.html#Alert Because you probably used *Save As* which leaves in a few useless References that causes issues.