RE: Shared MDB Performance with Access and ASPNET Clients
- From: "DavidT via AccessMonster.com" <u34312@uwe>
- Date: Thu, 01 Oct 2009 14:56:25 GMT
Is this database a front end or a back end?Back end Access 2003 database with only tables.
It is a split database? If so, where does the front end reside?Yes. Front end resides on each client computer.
Are multiple users accessing the same front end?No.
Can you describe how you are using OLE in this situation?OLE used in the connection string of the ASP.NET web.config
(Provider=Microsoft.Jet.OLEDB.4.0).
Front-end Access client program file uses both OLE and ODBC. Front end is
linked to most tables in the back end database via DAO ODBC connection.
There are some tables that are not linked to the front end containing program
user names. Data from these tables is retrieved via ADO using the OLEDB
provider (Provider=Microsoft.Jet.OLEDB.4.0).
Yes. I have given all users full permissions to make sure nothing is left out.You say the users all have modify permissions where the mdb file is located,
does that mean read, write, create, delete? That is what is required.
--
DavidT
Austin, TX
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-externaldata/200910/1
.
- Follow-Ups:
- References:
- Prev by Date: 97945
- Next by Date: RE: Shared MDB Performance with Access and ASPNET Clients
- Previous by thread: RE: Shared MDB Performance with Access and ASPNET Clients
- Next by thread: RE: Shared MDB Performance with Access and ASPNET Clients
- Index(es):
Relevant Pages
|