>but I needed to know if mulit-users was allowed at all in Access.
As I said in my previous post- in theory (that's what MS claims) 'yes'.
In practice- it's a pain in the neck, surely if the mdb file is on the network
(and this what you're going to have since you're talking about multi-user environment). The things become even worse if the file is "big"
>is it any different to open/use in Visual Basic 6 compared to Access?
It's, at least in that sense that MSDE is a 'real' database engine and Access
just "all-in-one" file, hence you have much more possibilities in MSDE (think of stored procedures, triggers, etc etc)
>Also, I was reading somewhere that if I use access with ADO then I can get it to work in a multi-user environment, is this true? If so, how?
Also, I was reading somewhere that if I use access with ADO then I can get it to work in a multi-user environment, is this true?
Well, you CAN get it to work - just not as well as you can with other solutions.
I can drive nails with a big wrench, too. But, not as easily as with a hammer. And my fingers will get sore.
Access was designed for single-user, desktop work. Although multiple user access was "bolted on" later, Access just can't work as well for multiple users as a server-based solution.
Last edited by loquin; 05-14-06 at 23:31.
"Lisa, in this house, we obey the laws of thermodynamics!" - Homer Simpson
"I have my standards. They may be low, but I have them!" - Bette Middler
"It's a book about a Spanish guy named Manual. You should read it." - Dilbert