Re: creating tabes with full schema name
- From: "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
- Date: Wed, 6 Sep 2006 11:25:19 -0400
Yeah, ADP has a lot of trouble with full schema name, especially when it's
not dbo by default (ie, you are not part of the owner database role (dbo)).
Also, it has the very bad habit of adding the current user as the schema
name to many calls to the SQL-Server. For example, if your user name is
MyName and you want to call the stored procedure dbo.MyProcedure, it will
often call MyName.MyProcedure instead, making it impossible to find
dbo.MyProcedure.
On forms, you can set the Record Source Qualifier and for control, you can
add the schema name to the Row Source but it's probably a better idea to
always use dbo and set everyone to dbo when you want to use ADP against a
SQL-Server.
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF
"mcnews" <mcourter@xxxxxxxxxxxxxx> wrote in message
news:1157552159.397193.35850@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Access ADPs do not seem to reckognize full schema name i.e.
dbo.mytable.
?
.
- References:
- creating tabes with full schema name
- From: mcnews
- creating tabes with full schema name
- Prev by Date: creating tabes with full schema name
- Next by Date: Re: Cannot open table in ADP
- Previous by thread: creating tabes with full schema name
- Next by thread: Re: Cannot open table in ADP
- Index(es):
Relevant Pages
|
