Have you tried to log into the machines that do not work with your login? if yes and it works, then it is a permissions issue.
Do the computers where the ADP works belong to people that have different permission levels on the SQL Server than hte ones where the ADP does not work? if yes, again permissions.
An ado object will run as long as you have given permissions to the user. If the dbo.Storedprocedure1 is the recordsource to your stored procedure and you make the Recordsource just Storedprocedure1, Access will add the dbo.Stooredprocedure1 or Storedprocedure1(dbo), which is not the same as Storedprocedure1.
In ado as long as the user has rights to execute the stores procedure, it will run well, but the user "MUST HAVE RIGHTS" to the stored procedure.
if dbo.name work on one machine that had problems, changces are iot will work for all other computers, but you must give them an updated front end. Try to automate the distribution of your front end to ensure that you can propagate a fix easily.
I would use ADo simply because i know it works and also because if i am using a stored procedure either via ADo or other method, the data is not updateable anyway and i can re-use the same code over and over for my forms and reports.
Sal
|