=> dbo. prefix renders SQL stored proceedures unknown

  • Thread starter Thread starter Rhonda Fischer
  • Start date Start date
R

Rhonda Fischer

Hello,

When I develop in Access 2000 on my computer with SQL
Server loaded I create stored proceedures
which work without error. However when I release the
application to users the error seems to be
that a dbo. prefix is automatically added to all stored
proceedures which deem them unknown.

How can I create queries recognised by other machines? I
tried adding a dbo. prefix without success:
errmsg:

ADO error: The object 'dbo.[dbo.spTodaysInLoads]' does not
exist in database 'TurnersMgmtSystem'

What should I do?

Thank you kindly
Rhonda
 
When you link up the tables, views, and stored procs, simply remove (rename)
the dbo prefix in the Access database window.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access

Rhonda Fischer said:
Hello,

When I develop in Access 2000 on my computer with SQL
Server loaded I create stored proceedures
which work without error. However when I release the
application to users the error seems to be
that a dbo. prefix is automatically added to all stored
proceedures which deem them unknown.

How can I create queries recognised by other machines? I
tried adding a dbo. prefix without success:
errmsg:

ADO error: The object 'dbo.[dbo.spTodaysInLoads]' does not
exist in database 'TurnersMgmtSystem'

What should I do?

Thank you kindly
Rhonda
Click to expand...
 
Hello Arvin,

Thank you for your response.

When I create an .ade, I place the application in a
directory of which is placed on peoples desktop using
a .bat file. There are quite a few users that will
receive this application, and as their computers do
not have SQL Server loaded locally it seems the queries
and tables are relabled only on these computers and
don't work - the forms just appear blank. They are fine
on my computer with SQL Server loaded and do not
appear with any dbo. prefix.

I'm not sure how I would rename the queries deleting the
dbo. prefix, unless I kind of copied the .adp into a
directory accessible to all and then go through all the
queries deleting the .dbo prefix? I'm a bit confused
how I can release my application in a working state.

Sorry, it's just that I don't actually link tables
for then to have the dbo. on my computer, it just seems
to appear linked with placed on a computer without
SQL loaded :/

If you have any more thoughts that would be terrific,
unless I haven't quite understood your drift.

Thank you kindly
Rhonda


-----Original Message-----
When you link up the tables, views, and stored procs, simply remove (rename)
the dbo prefix in the Access database window.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access

Hello,

When I develop in Access 2000 on my computer with SQL
Server loaded I create stored proceedures
which work without error. However when I release the
application to users the error seems to be
that a dbo. prefix is automatically added to all stored
proceedures which deem them unknown.

How can I create queries recognised by other machines? I
tried adding a dbo. prefix without success:
errmsg:

ADO error: The object 'dbo.[dbo.spTodaysInLoads]' does not
exist in database 'TurnersMgmtSystem'

What should I do?

Thank you kindly
Rhonda
Click to expand...


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.556 / Virus Database: 348 - Release Date: 12/26/2003


.
Click to expand...
 
Rhonda Fischer said:
I'm not sure how I would rename the queries deleting the
dbo. prefix, unless I kind of copied the .adp into a
directory accessible to all and then go through all the
queries deleting the .dbo prefix? I'm a bit confused
how I can release my application in a working state.
Click to expand...

Bingo! That's exactly how it's done. Place your already properly linked copy
on the server and let your users download it to their workstations. I use
UNC in my connection strings, but it is even easier to use mapped drives.

The only time I've seen views and stored procs being renamed with the dbo
prefix is when they are imported as tables, instead of linked. It's the
tables you need to rename in your application.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
 
Back
Top