Just share it so that it's accessible as a network share ("\MachineNameShareNamemyDatabase.mdb").<BR><BR>Th en use the fully-qualified network share name in your connection string.<BR><BR>The main problem with this approach is permissions. But it's certainly possible.<BR><BR>Craig.
Error Type:<BR>Server.MapPath(), ASP 0174 (0x80004005)<BR>An invalid '/' or '' was found in the Path parameter for the MapPath method. <BR><BR>I've shared the folder that the DB sits on. Do I have to share the folders above that one?
Show what you're trying to do.<BR><BR>If you're using this approach (passing "\MachineNameShareNamemyDatabase.mdb"), then you DO NOT NEED Server.MapPath().<BR><BR>Show me your connection string and I'll fix it for you.<BR><BR>Craig.
Now I'm getting the error I usually would get if I didn't have the Read/Write Permissions set up correctly. <BR><BR>Error Type:<BR>Microsoft OLE DB Provider for ODBC Drivers (0x80004005)<BR>[Microsoft][ODBC Microsoft Access Driver]General error Unable to open registry key 'Temporary (volatile) Jet DSN for process 0x424 Thread 0x71c DBC 0x2180014 Jet'.<BR><BR><BR>But, I've given Everyone Full Control, so that's not the issue...<BR>Any ideas?
I think it is still a permissions issue...<BR><BR>Have you ever used an OLEDB connection? I'd do that as my first step. Then, you need to check NTFS permissions, and permissions on the share as well (depending on the OS, this may be the same).<BR><BR>Craig.
OLEDB isn't a methodology exactly. It's using another driver.<BR><BR>http://www.able-consulting.com/ado_conn.htm (or .html, can never remember).<BR><BR>Find "OLEDB Driver for Jet" - that's the broad MS name for a driver that incorporates the Access driver. It tells you on that site how to write a connection string using it.<BR><BR>Craig.