persistendt recordset

[DADAZHU]

Hi, guys,

I understand that it is a good idea to have a shared backend batabase in a multiple user environment. I also learned that seting up a persistent recordset connection fixes the problem for LDB locking, and it will significantly improve the performance when two or more users are in the database.



I am planning to use excel templates and ADO connection to communicate with a shared backend db for my new project, and there will be multiusers. My question is, do I need to set up a persistendt recordset in this case?

I have done some Excel tools and templates in the past, I often use them to read and write data to access database, but most of them are used by a single user.

Your help is greatly appreciated.

David

[rpeare]

Why involve excel at all if the back end is access? you can set up data entry forms to be way more versatile than excel can be (i.e. preventing data entry that doesn't meet specific minimum data requirements etc). What you're proposing is an extremely cumbersome way of handling the power of a database.

[DADAZHU]

Hi, rpeare,

Thanks for your reply. At where I work, only few users have access to Access, but every user can use Excel, obviously using Excel tool as an 'Front end' for the new database will save a lot of dolloars to buy the users' licence for Access. Although I have to admit that this way will take much more time.

Can you recommend an source where I can get a example of Access database including FE and BE? thanks.