Updating a multi-user MDB through ODBC

  • Thread starter Thread starter asdf
  • Start date Start date
A

asdf

I have a multi-user (shared) Access database that I'd like to update
remotely via a web service or asp.net page. The database has about a 5 user
average load, and it shouldn't peak above 10 users. Historically, every
time I've looked into doing anything fancy like this with Access, I've
discovered that Access is easily corrupted. Has anything changed as far as
this is concerned? We're running the latest versions of IIS, Access, and
Windows Server 2003, all up to date on patches. What other options can we
consider? Thanks.
 
I have a multi-user (shared) Access database that I'd like to update
remotely via a web service or asp.net page. The database has about a 5 user
average load, and it shouldn't peak above 10 users. Historically, every
time I've looked into doing anything fancy like this with Access, I've
discovered that Access is easily corrupted. Has anything changed as far as
this is concerned?
Click to expand...

Not really. Though we don't experience "easy corruption" issues with
Access.
We're running the latest versions of IIS, Access, and
Windows Server 2003, all up to date on patches. What other options can we
consider?
Click to expand...

MSDE, Microsoft SQL Server, MySQL, etc.

Jeff
 
asdf said:
I have a multi-user (shared) Access database that I'd like to update
remotely via a web service or asp.net page. The database has about a 5 user
average load, and it shouldn't peak above 10 users. Historically, every
time I've looked into doing anything fancy like this with Access, I've
discovered that Access is easily corrupted. Has anything changed as far as
this is concerned? We're running the latest versions of IIS, Access, and
Windows Server 2003, all up to date on patches. What other options can we
consider? Thanks.
Click to expand...

As Jeff has suggested, there are plenty of other systems you could use.

But although Access was not designed for this kind of work, I dont see why
it cant do the job, nor why you would be prone to corruption.

MSDE might be a good compromise. You can develop it in Access, the 'upgrade'
it to MSDE, and take advantage of some of the benefits of SQL Server.
Performance will suffer for > 5 concurrent users, but if this is a problem
you will already be halfway to SQL Server...
 
Dear Jeff,

you might want to consider evaluating Virtuoso, a universal server
which will fulfill all your requirements without any additional
requirements.

You can utlilize its very own database or alternatively link your
Access DB into its Virtual database, then accessing the data via its
SOAP capabilities by e.g. exposing Stored Proecudures as Webservices
using a few mouseclicks only
or accessing your data using its very own .NET Provider.

PLease refer to http://www.openlinksw.com/virtuoso/ for more details.

If you do have any questions please do not hasitate to contact us.

Kind Regards,

Jan Csisko
Professional Services Consultant
OpenLink Software Web: http://www.openlinksw.com
Product Weblogs: Virtuoso:
http://www.openlinksw.com/weblogs/virtuoso
UDA: http://www.openlinksw.com/weblogs/uda
Universal Data Access & Virtual Database Technology Providers
 
Back
Top