multiuser database and changes

[Indigobuni]

I have a timesheet database that is going to be used by multiple users at the same time. More than one person can enter their data in on a separate record. I was also in it and was trying to make changes to a different form. It told me I may not be able to save the changes I was making.

How can I set the options for the database, so that for example, Mary is in the timesheet form entering her time and Jennifer can enter into the design of the expense report form to change a couple of things and save it. Thanks.

 

[mission2java_78]

Do a search on the forum...

Split your db is the ideal situation...than make sure you check record locking options and nt security.

Jon

 

[Indigobuni]

Not sure what you mean by split it. The db is housed on a network drive. This is a small office (approx. 14 people would be entering their timesheet), so I can't imagine that more than 2 people would be entering their timesheet at the same time.

My options are set as: Shared, No Locks, Open databases using record level locking (checked).

The problem is once someone enters their time. They go to a query and in the design mode, enter their name and the From/To Date. Save it and print out the report attached to the query. But, if someone else has the db open, when they try to save the query, they get that error about changes not being saved.

I don't want this to get too complicated by having to do all this stuff to the db just to make it run. It may not be worth even keeping it.

 

[Mile-O]

Not sure what you mean by split it.

By splitting a database you have one back end that only has the database tables and each person has their own front end which is everything else: modules, forms, queries, macros, reports, and the tables in the front end are linked to the back end.

There have been numerous posts regarding splitting a database and Access also has a Database Splitter Wizard under:

Tools -> Add Ins -> Database Splitter

 

[mission2java_78]

Your end users are getting into the design view of your db?????

Well no wonder!!!! Why are you allowing that to happen? You should provide your querying functionality via a form or input box...not inside the design view of anything. That is why you are receiving a message that the db is blah blah blah...

Jon