with access, (i think) it's all down to file access speed. the table gets locked and unlocked as users hit it, so the max number of users is determined, basically. by how well you code the ASP. badly coded ASP/Access can be awful, but code it well and it'll be fine<BR><BR>j
i don't understand what you mean by "coding well" ...<BR>anyways considering it is coded well....how may users can the database take????<BR>..also if i change it to sql ... where can i get resources about how to do it...how to set the connection ..change asp code...???
by 'coding well' i mean :<BR><BR>opening connections late, closing them early<BR>destroying objects asap<BR>doing the bare minimum of processing to accomplish an end result<BR>understanding how ASP uses and recovers memory<BR>cutting down on context switches<BR>knowing when to concatenate, and when to output multiple times<BR>not putting long rambing html blocks in between your ASP procedures<BR>etc... etc...<BR><BR>it all comes with experience<BR><BR>changing to SQL Server is a surprisingly small step (apart from the cost). there are resources all over the web on it<BR><BR>www.aspin.com is a good starting point
I have tried to deal with the same issues. Some posts have indicated that Access can support 5 concurrent users. My small site does not do very well. And I feel like I have it coded correctly. Most people suggest using the Microsoft OleDB 4.0 Jet. I have not had a chance to use that because my provider will not support dsn less connections. If there is anyone out there who has had success with concurrent users to Access97, I would like to hear what driver/provider you are using.