S
SteveMc
We currently use an Access Project (ADP) with a SQL Server 2000
backend. I'm currently making some changes to the project, and am
finding that as the ADP size increases (18/19 MB) I am having more
problems with user testing. Users have Access Runtime 2003 on their
desktops, and they are getting the message that an error has been
encountered, and Access will backup and repair project (which doesn't
stop the fault from happening again).
Tried de-compiling, and importing forms reports etc into blank ADP, but
only converting ADP into ADE seems to solve the problem.
Are there any known problems with using ADE files with Runtime Access
(apart from not allowing design view)?
Will I need to re-test the whole project to make sure the ADE hasn't
stopped any features from working?
Thanks.
backend. I'm currently making some changes to the project, and am
finding that as the ADP size increases (18/19 MB) I am having more
problems with user testing. Users have Access Runtime 2003 on their
desktops, and they are getting the message that an error has been
encountered, and Access will backup and repair project (which doesn't
stop the fault from happening again).
Tried de-compiling, and importing forms reports etc into blank ADP, but
only converting ADP into ADE seems to solve the problem.
Are there any known problems with using ADE files with Runtime Access
(apart from not allowing design view)?
Will I need to re-test the whole project to make sure the ADE hasn't
stopped any features from working?
Thanks.