MsAccess/ADP - record source doesn't exist

[usenet_e]

Hello,
few users have problems with our application
(ADP/MsAcces2000+SqlServer2000). When
they want to open a report which source is a stored procedure, they get

message that "record source specified..... do not exist" - of course,
it's not true.
More details:
- other users don't have this problem
- they have WinXP
- all users have the same permissions to SQL objects
- I've checked Microsoft KB
(http://support.microsoft.com/kb/243532/en-us) and they write about
"dbo." before source name - I use that, so it's not a solution. What
more, in application there are lists which have SP as row source and
without "dbo." and it works. (In lists a row source is defined as:
"exec <sp_name>", in reports as: "dbo.<sp_name>").
- computers have all service packs, new version of MDAC, etc.
- I asked another user, who doesn't have this problem on his machine,
to login on "bad" machine and he couldn't open reports too.

Maybe someone could help? because I don't have more ideas.

[Oscar Santiesteban]

have you tried making the source just SQL Text and saying "exec dbo.[your
procedure name"? Just a thought?
"usenet_e" <gr*********@gmail.comwrote in message
news:11********************@m73g2000cwd.googlegrou ps.com...

Hello,
few users have problems with our application
(ADP/MsAcces2000+SqlServer2000). When
they want to open a report which source is a stored procedure, they get

message that "record source specified..... do not exist" - of course,
it's not true.
More details:
- other users don't have this problem
- they have WinXP
- all users have the same permissions to SQL objects
- I've checked Microsoft KB
(http://support.microsoft.com/kb/243532/en-us) and they write about
"dbo." before source name - I use that, so it's not a solution. What
more, in application there are lists which have SP as row source and
without "dbo." and it works. (In lists a row source is defined as:
"exec <sp_name>", in reports as: "dbo.<sp_name>").
- computers have all service packs, new version of MDAC, etc.
- I asked another user, who doesn't have this problem on his machine,
to login on "bad" machine and he couldn't open reports too.

Maybe someone could help? because I don't have more ideas.