S
Steve McManus
Our Access project file (.adp) is distributed as an .ade (users only
get runtime Access 2003).
Within project we use SimpleOCR objects (SimpleOCX.dll) to implement
scanning functionality.
I recently created a new release on my machine - extracted the .ade
file for users, and now when someone tries to scan document (on
machine with local scanner attached) it comes up with the 403 Class
does not support Automation error.
If I revert back to previous .ade file it works again.
Seems to be a problem with how my machine built the .ade file, have
tried re-registering .dlls with no luck.
Even when I try to create .ade files from previous (proven) versions
of .adp file it now causes the 403 error.
Can anyone think what I can check on my machine to sort this?
Thanks.
get runtime Access 2003).
Within project we use SimpleOCR objects (SimpleOCX.dll) to implement
scanning functionality.
I recently created a new release on my machine - extracted the .ade
file for users, and now when someone tries to scan document (on
machine with local scanner attached) it comes up with the 403 Class
does not support Automation error.
If I revert back to previous .ade file it works again.
Seems to be a problem with how my machine built the .ade file, have
tried re-registering .dlls with no luck.
Even when I try to create .ade files from previous (proven) versions
of .adp file it now causes the 403 error.
Can anyone think what I can check on my machine to sort this?
Thanks.