Multiple User database without splitting

Question

Hey,

I am currently creating a database to hold the results of quality control testing and am wondering how I can have multiple users accessing the database without having to split the database.

The reason behind not splitting the database is that we are testing virtual clients, and I dont want to have our testers have to copy the whole front-end for each new test cycle, considering we get a new cycle (and therefore a fresh database) approximately each week.

Is this possible? Or do we HAVE to split the database. Furthermore, after the test cycle is complete, can you delete the front-end or do you lose the data that is saved there? Can multiple users access a single front-end?

Many thanks,

Greg

Answer 1

Try running a Debug before splitting. But yes, you can create a Blank database and import just the tables into it. Then delete the tables from your front end and link to the tables in the back end you just created.

Answer 2

Ah cool, just wondering whether there was an alternative. Is there a way to manually split the database? It is currently returning an error 'Subscript Out of Range' and only splitting 1 table away from the rest of the database.

Thanks,

Greg

Answer 3

The reason behind not splitting the database is that we are testing virtual clients, and I dont want to have our testers have to copy the whole front-end for each new test cycle, considering we get a new cycle (and therefore a fresh database) approximately each week.

 

 

Why not? If you setup this up properly, copying a new front end should be very easy. But then I question why a new front end is needed at all. Your database should have a table of test cycles. Each time a new test cycle is is added, the user chooses the test cycle to work on and results entered are attributed to that test cycle. Completed test cycles can be marked as completed so new data can't be entered to them. 

Splitting a database is an absolute requirement for any application that will be used by multiple users. There are several reasons why splitting is required. And your reason for not splitting doesn't fly.

Answer 4

Re your last question: think about it. If all tables, queries, forms, and reports are in 1 file and you delete that file, do you still have the data (which is stored in the tables)?

This is one of the reasons why we split databases: that you can continue to improve the FE while keeping the data safe in the BE.

Sharing the same monolithic database is possible but not advisable. You increase your chances for locking issues and corruption.

"Copy the whole FE for each new test cycle"? It seems that would not be necessary if we used a bit more flexible database design and application.