dbo.anyreport does not exist message in 2007 data project

[Da-Geek]

Frustrated! I have built a small application on Access 2007 with a SQL 2000
backend data base. It all works great on my development laptop. I package and
deploy it on the clients using the Access 2007 runtime, installs great, you
can enter and find data, but with all the reports it comes up with an error
message that the dbo.anyreport does not exist. I always loved this product,
but 2007 is a real challenge! Any ideas or help greatly appreciated.

 

[Richard]

Hi Ray,

Frustrated! I have built a small application on Access 2007 with a SQL 2000
backend data base. It all works great on my development laptop. I package and
deploy it on the clients using the Access 2007 runtime, installs great, you
can enter and find data, but with all the reports it comes up with an error
message that the dbo.anyreport does not exist. I always loved this product,

Just a thought here, isn't [dbo] for linked tables? I am no expert but
looking at my database only my tables have the dbo prefix. Everything else
resides in the frontend.

but 2007 is a real challenge! Any ideas or help greatly appreciated.

Richard

 

[John W. Vinson]

Hi Ray,

Frustrated! I have built a small application on Access 2007 with a SQL 2000
backend data base. It all works great on my development laptop. I package and
deploy it on the clients using the Access 2007 runtime, installs great, you
can enter and find data, but with all the reports it comes up with an error
message that the dbo.anyreport does not exist. I always loved this product,

Just a thought here, isn't [dbo] for linked tables? I am no expert but
looking at my database only my tables have the dbo prefix. Everything else
resides in the frontend.

but 2007 is a real challenge! Any ideas or help greatly appreciated.

Richard

dbo ("data base owner") is the default prefix for SQL/Server linked tables. My
guess is that the SQL 2000 backend on the developmental laptop contains a
table named anyreport, but that said table does not exist in the production
SQL environment.

 

[Da-Geek]

Nah...i used anyreport be none of them work at all, get the same message no
matter what I do and the dev laptop works fine....cllient runtime will not!
--
Da-Geek

Hi Ray,

Frustrated! I have built a small application on Access 2007 with a SQL 2000
backend data base. It all works great on my development laptop. I package and
deploy it on the clients using the Access 2007 runtime, installs great, you
can enter and find data, but with all the reports it comes up with an error
message that the dbo.anyreport does not exist. I always loved this product,

Just a thought here, isn't [dbo] for linked tables? I am no expert but
looking at my database only my tables have the dbo prefix. Everything else
resides in the frontend.

but 2007 is a real challenge! Any ideas or help greatly appreciated.

Richard

dbo ("data base owner") is the default prefix for SQL/Server linked tables. My
guess is that the SQL 2000 backend on the developmental laptop contains a
table named anyreport, but that said table does not exist in the production
SQL environment.

 

[John W. Vinson]

Nah...i used anyreport be none of them work at all, get the same message no
matter what I do and the dev laptop works fine....cllient runtime will not!

Does the client runtime have an ODBC connection to the SQL server, and
appropriate permissions to use the database?

 

[Sylvain Lafontaine]

My guess would be that the owner of the table anyreport is not dbo. but
another user on your production machine.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)

 

[Da-Geek]

I have checked security, tried loging on as myself on the client, still get
the same error. The only difference is that I have a full version on my
laptop and the clients are using the runtime. Every thing on the SQL Sever
seems to be in order as well as the ODBC connection. As I stated you can do
any upates or adds on the forms, this only effect reports.