>>Does anyone know what the limits are for the number of concurrent users accessing an Access database from an Access application across a network without using SQL?
>>
>>I am trying to explain to a client why I decided not to use Access for a VFP application that I am developing for the client. After the client has made many many changes from the original specs (which were't much), they are curious to know why it is taking so long. The manager wanted to know if the original app could be done in 2 weeks. I told him that 2 weeks was very unrealistic and 2 to 6 months would be more like it depending on what they wanted to ad. It is a system to manage and track production on 16 production lines as well as the employee's pay rate applied to each of the lines that are producing products and who worked on a given line for a given day. There are all kinds of neat little things that weren't ever documented in the original spec used for estimating time on the project. Such as Rate Premiums for the shift the employee worked which is also by the way different than the premiums for the same shifts for temporary workers as well as, Oh by the way there are Temporary
>>Team leaders that also get an additional amount per hour if they are designated as such for that day. So far I have spent 250 man hours on the project and they can't believe it has taken so long.
>>
>>It kind of made me doubt me skills for a bit until I again reviewed their original documentation with them again and pointed out all of the unknown changes asked for. Now everything has to be done in writing.
>>
>>I was quite miffed when they asked why I hadn't used MS Access because they were sure that it wouldn't have taken so long. I haven't listed all of the other validation requests and Scrap Materials conversion factors and bucket weights and unit conversions that were added as well.
>>
>>Sorry, too much venting here! :-)
>>
>>Does anyone know how many clients Access supports to a database using NT Server? They have to have 20 - 35 workstations talking to this database at the same time.
>
>
>20 is waaaaaaaaaaaaaaay too many. 4-5 MAX.

And even 4-5 is too many if there are large tables and frequent lookups.