We developed an Access Data Project (ADP) application. It is compiled as an
ADE and connects directly to a SQL Server database. Each user has their own
local copy of the ADE file to connect. Our development manager would like
for us to have a single copy of the ADE file on a network share to eliminate
the need to distribute the ADE to each desktop.
A preliminary test shows displays a file sharing error.
I think I remember reading on MSDN that this was not possible? If not, are
there other alternatives.
Even if this is possible (and it probably is), it would not be desirable.
You would experience significant perfomance reductions and frontend/backend
corruption would quickly become a frequent event. Tony Toews has a
AutoUpdater on his site that eases the burden of delivering frontends to
users (can't remember the address, Google on his name and you'll find it).
I'm not sure it works with ADEs, but you can check it out.
> We developed an Access Data Project (ADP) application. It is compiled as an
> ADE and connects directly to a SQL Server database. Each user has their own
[quoted text clipped - 6 lines]
> I think I remember reading on MSDN that this was not possible? If not, are
> there other alternatives.
shardobe@adelphia.net - 19 Nov 2003 16:05 GMT
Scott, thanks for the response. I thought the corruption problem only
happens with MDE files and not ADE files. I don't think a SQL Server
database would get corrupted.
As for the AutoUpdater, I did read a little bit about it. Sounds like it
could solve the problem.
Scott McDaniel - 20 Nov 2003 11:59 GMT
SQL Server database can get corrupted; however, I'm speaking of the Frontend
... with multiple users using the SAME copy of your frontend, you will
almost certainly cause problems. The performance issues alone, however,
would cause me to rethink this strategy and convince your colleague of the
necessity of distributing individual frontends to each user.
> Scott, thanks for the response. I thought the corruption problem only
> happens with MDE files and not ADE files. I don't think a SQL Server
> database would get corrupted.
>
> As for the AutoUpdater, I did read a little bit about it. Sounds like it
> could solve the problem.
shardobe@adelphia.net - 21 Nov 2003 16:44 GMT
OK. Thanks Scott. Appreciate the help