J
James A. Fortune
Rick said:Well that configuration is how most of my apps are set up, but I have no idea
what the maximum concurrent user limit for one particular form/table combination
would be.
Then I think I'll wait a while longer before testing those limits.
Not sure how that relates to "forms on the internet" since an Access form cannot
be run over the internet.
I was speculating about potential future products. Visual Studio has
some controls that have some data binding capabilities but I'm not sure
whether or not they were designed to deal with concurrency issues.
Visual Studio also seems to have a much better plan in place than Access
for dealing with multithreading. So it seems possible that, given
multiuser success with bound forms in Access with a SQL Server backend,
a market might exist for an Access-like product (motive) to be created
with Visual Studio (means) that would allow for bound forms on a website
and take advantage of multicore processors on the client. Using a
locking file is certainly possible. It would save me the trouble of
implementing my own collision resolution code, which I have done before.
I'm still not sure that I could trust the whole bound form on the web
concept yet.
James A. Fortune
(e-mail address removed)