DougStevens
Programmer
Need assistance with an error on a ADP file. A week ago I've installed a SQL server and with a ADP file as the front end. The installation and tests were successful.
Now, whenever the user is experiencing errors with this ADP file. Here is the gist of the issues/errors that appear to be related:
1. Whenever running a macro which uses the "OpenStoredProcedure" action, it can not find the stored procedure.
2. Whenever a form is open that is based off a view or table, it results in an error. (FYI, forms based off a SQL statement are behaving normally.)
3. Whenever a report that is based off a view is open an error occurs.
The error usually describes that MS Access can not find the object <object name>.
Here's the twist, the user can open the views, tables, and execute the store procedures from the database window.
In some situations, the user can open the macro, form, or report into design view, reassign the RecordSource or StoredProcedureName property and it will work fine, for awhile.
The users are running MS Access 2002.
Is this a connection issue?
Is this An MS Access version issue?
Is this a SQL Security issue?
Now, whenever the user is experiencing errors with this ADP file. Here is the gist of the issues/errors that appear to be related:
1. Whenever running a macro which uses the "OpenStoredProcedure" action, it can not find the stored procedure.
2. Whenever a form is open that is based off a view or table, it results in an error. (FYI, forms based off a SQL statement are behaving normally.)
3. Whenever a report that is based off a view is open an error occurs.
The error usually describes that MS Access can not find the object <object name>.
Here's the twist, the user can open the views, tables, and execute the store procedures from the database window.
In some situations, the user can open the macro, form, or report into design view, reassign the RecordSource or StoredProcedureName property and it will work fine, for awhile.
The users are running MS Access 2002.
Is this a connection issue?
Is this An MS Access version issue?
Is this a SQL Security issue?