Access 2007 splitting a database

I have a database which I have made copies of and have been splitting. There will be more than 10 people who will use this database at any one time. The users need to be able to input and save data.

I have experimented with two people simultaneously usine the same front end. Although we could both access forms at the same time and create new records as soon as we tried to save it would not let both of us.

I then made a copy of the front end so we both had one each. This time it allowed us to save however what I saved on my front end did not appear on the other users front end.

I need to be able to have multiple using the database at once, being able to save and view reports at the same time and have any changes made by one user show up on all other users front ends once it is saved. Can anyone help me?
BartzincAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Your second scenario would be the correct one - each user should have their OWN copy of the FrontEnd. Users would have to periodically refresh their data, which would refetch those new records.

What do you mean by "save and view reports"? Are you going to allow users to build or alter reports? If so, then those changes would NOT be shared by others (and this can lead to some serious corruption issues also).
0
BartzincAuthor Commented:
Hi,

I wish users to be able to save inputed data and be able to view reports that have already been created. They will not be building or altering anything in regards to the design of the front end. Just want them to be able to input and view.

As I have mentioned above I have trialed using two front ends and the saved new records would only appear on the front end on which they were saved. Even after both front ends were closed and reopened. We need any saved input data changes to be reflected. Can you advise as to how I can make this happen.  

0
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
You're not doing something right.

If BOTH frontends connect to the SAME BACKEND, all users will be able to see this.

Did you split the database, then place the backend on a publicly available location, then supply a copy of the FE to each user?
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

BartzincAuthor Commented:
I have just tried to split a copied version of the original database.

It has come up with a message
Subscript of of range

What does this mean?
0
BartzincAuthor Commented:
Sorry message should read
Subscript out of range
0
BartzincAuthor Commented:
If you have split a database should you still be able to see the tables in the front end file?
0
BartzincAuthor Commented:
I think the problem lies with the database not splitting properly.

I need someone to help me work out why I keep getting the message
"Subscript out of range"

This seems to be the problem
0
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
You'd see "links" to the tables in the frontend file. Opening them will look just like opening a local table. Trying open them in Design view, however, will produce an alert message (i.e. you can't Design linked tables).

Splitting a database does this:

1) Removes the tables from the file and places them in another database
2) Creates links to that other database from the original

If you're having troubles with the splitter wizard, you can do this manually:

1) Create a new, blank database. If this is going to be shared, then do so in a publicly available network resource - i.e. a folder that is shared, and can be accessed by all your users on that network.
2) Click File - Get External Data - Import
3) Locate your original database and import all TABLES except for those beginning in MSys ... those are system tables, and Access will create them for you. If you don't see any system tables, click Tools - Options and check the box so that you can view System and Hidden tables.
4) Close the new database
5) Open the original database
6) Delete all tables
7) Click File - Get External Data - Link.
8) Locate the database you created in Step 1 and select all tables except those beginning with MSys.

Your database should now be linked. You now deploy ONLY the original database to your users. Each copy of that db is now linked to the same Backend file, so as users enter data it will all go into that file.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
BartzincAuthor Commented:
Thankyou
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.