Testing for multiple users with one PC

[speedball]

Hello all

I'm building an access database that will eventually be used and edited by multiple users at the same time over a LAN.

Is there a way that I can test how the database will respond to multiple users using just my own PC, i.e. opening the database twice, as different users and seeing how it responds?

I realise that I could put it on a network and have two computers side by side but running the database, but I spend most of my time developing it from home where I don't have access to the network that it will eventually be on.

Thanks
speedball

 

[Fifty2One]

You could get a couple of low grade second hand PCs at home and a router and simulate a couple of users for your database. I also find that off base development works better with downgraded clock speed computers as that will compensate for client/server lag times. No end user likes slow software, developing on slow machines gives you some attention to response times also.

 

[datAdrenaline]

Hopefully you have a split configuration in with there is a Front End (forms, reports, queries, code, and LINKED tables) and a Back End (data tables only) ... with the intent of having EACH user having THERE OWN copy of the Front End ....

With that being the premise, then simply make a copy of your FE as another name, then open both FE's on your machine.
...
Another option is Microsofts Virtual Machine.

 

[speedball]

Thanks for the responses guys

I was intending to split the database just before releasing it to other users, but in light of datAdrenaline's suggestion I'll split it next time I work on it.

Thanks again
speedball

 

[DCrake]

One preconception I see regularly is that developers create applications in an unsplit environment, then just prior to deployment they attempt to split it between FE and BE. In most cases this is fine, however on some occassions, depending on how the app was written, errors occur. I cannot see why the application is not split at the point of creation, that way any issues are evident during early development and can be rectified earlier.

It may be that the error(s) that is/are raised when the app is plit is/are major elements of the application and the resolve can take a considerable amount of re-programming to complete. Even for single user applications that I have written in the past I have always started with a split application, ok, switching from FE to BE to make table changes is a bugbare, but at least I am in full control of the app.

David

 

[speedball]

Thanks David

I think splitting at an early stage is going to be the way forward for my future databases.

speedball