Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Report problem

Status
Not open for further replies.

OCM

MIS
Sep 12, 2002
222
US
Greetings,

Using Access 2000, I have designed & deployed a server-based database table (Be) in the server and distributed the (Fe) to about 10 – 12 users machine. They start using the database since March and so far entered about 5000 records and there was no problem. One day they entered a lot of records but, when they run the report they didn’t get the numbers right (they got only few records). I took a look at the table (audit trial) for that given day, they entered 250 records. Although I have a Save Record button, they really do not need to use it (when they click Next Record button it usually saves it for them)
1. What can be the cause and where would be the first thing to look at?
2. How often do you have to Compact/Repair the database
3. The database is growing very fast when do I need to make a decision to upsize it to Sql server?

Thanks,
OCM
 
1. I'd first make sure there is no filter applied to the report which shouldn't be there. Open the report in design view and look at the Data tab to check the Filter options.

2. I always try to compact and repair my databases once every 2-3 days. Obviously you would determine the frequency for your databases.

3. Depending on the complexity of your queries and your table structures within your current db, the amount of time it takes one to upsize a db and update/re-write anything can vary significantly. Keep this in mind when determining if/when you will be upsizing.



--
Mike

Why make it simple and efficient when it can be complex and wonderful?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top