Subdatasheet error on ADP projects in Access 2010

Grant Morgan

unread,

May 30, 2010, 7:42:01 PM5/30/10

to

Running Office 2010 Pro on Windows 7. Database connection to SQL Server 2008
via MS Access ADP.

When viewing a table datasheet in Access 2010 Database Project (ADP) linked
to SQL Server 2008 database, if you go to try to expand the subdatasheet to
show data in linked tables, you receive an error. If the master table is
named 'MASTER_TABLE', and the detail table is named 'DETAIL_TABLE' you
receive the message:
"The table or query name 'dbo.DETAIL_TABL' you entered in either the
property sheet or macro is mispelled or refers to a table or query that
doesn't exist." Note that the last character is dropped off the detail table
name - i.e. DETAIL_TABL instead of DETAIL_TABLE.

If you remove and re-link the subdatasheet, it then works OK and shows the
related data. But if you close and re-open the database and try to expand the
subdatasheet again, it will fail with the same error (even if you previously
saved the table).

This error only occurs in Access 2010 ADP's, and is not evident in a regular
Access Database with local table data.

This definately seems like a bug! Hoping someone can help me out.

Cheers
Grant

Virtual_One

unread,

Jun 1, 2010, 3:43:01 PM6/1/10

to

I too am experiencing the same issue except that I am connecting to SQL
Server 2005 via an ADP project in Access 2010.

Bob McClellan

unread,

Jun 1, 2010, 10:59:47 PM6/1/10

to

I do not have Office 2010 but...
Do you have the schema in the Record Source Qualifier showing dbo or
whatever the schema is?
I've seen this cause the probelm you are describing.
hth,
..bob

"Grant Morgan" <grant...@noemail.noemail> wrote in message
news:F62091B9-7065-4A18...@microsoft.com...

Grant Morgan

unread,

Jun 5, 2010, 1:17:28 AM6/5/10

to

Hi Bob

Table names not showing DBO - they are just showing the actual table name as
it is an ADP.

Was that what you meant?

G

Bob McClellan

unread,

Jun 5, 2010, 10:28:56 AM6/5/10

to

Grant,
In 2007..and 2003 .adp, on the property sheet for the form,
On the Data Tab
The first property is Record Source
The 2nd is Record Source Qualifier.
If the schema for the table or stored procedure being used in the Record
Source is dbo
then put dbo in the Record Source Qualifier.
I've seen the problem you are describing and found that simply putting the
schema in the
Record Source Qualifier was what was missing. Along those same lines.... if
the user
does not have permission for the schema you will see the same problem.

hth,
..bob

"Grant Morgan" <grant...@noemail.noemail> wrote in message

news:C7CA4A7F-8127-4116...@microsoft.com...

Grant Morgan

unread,

Jun 6, 2010, 10:35:27 PM6/6/10

to

I'm not using a form - this occurs in the table datasheet view.

Bob McClellan

unread,

Jun 7, 2010, 3:19:51 PM6/7/10

to

Grant,
Not sure what to suggest to you. I don't build anything where I allow
users
to work at the table level.

"Grant Morgan" <grant...@noemail.noemail> wrote in message

news:2830BA17-8C82-4216...@microsoft.com...

Grant Morgan

unread,

Jun 7, 2010, 5:57:43 PM6/7/10

to

Hi Bob

I agree - I don't let users to work at the table level, but every once in a
while it's useful if I need to change some data that hasn't had a UI written
for it....

I feel it is a genuine bug in the software - do you know where abouts I can
submit it as such to Microsoft?

G

a a r o n . k e m p f @ g m a i l . c o m

unread,

Jun 14, 2010, 6:12:13 PM6/14/10

to

I sure don't have this problem