Subdatasheet for linked SQLServer tables...

[Scott]

I have a SQL Server table that has a self joining relationship.
In Access 2002 (2000 format) I was able to link the table and set the 1 to
many relationship so that Access properly displayed the subdatasheet for all
related records.
After upgrading my machine to Access 2003 today, I find that the
subdatasheet is no longer displayed (no "+" symbol.)
I created a new mdb and linked the SQL table in again and set the 1 to many
relationship.
Still no go.
I did notice that Access monkeyed with the relationship when it saved it
though.
When creating the relationship I linked Table(PK) to Table_1(FK).
Upon editing the relationship after a save - I see that it is displayed as
Table_1(PK) to Table(FK).
Obviously a bug.
If I create a local table from the SQL table and set the 1 to many
relationship - everything works fine!

Any Microsoft MVP's out there have an idea?

 

[Duane Hookom]

I don't think any (could be wrong) Access MVPs use subdatasheets.

 

[Albert D. Kallal]

I have a SQL Server table that has a self joining relationship.
In Access 2002 (2000 format) I was able to link the table and set the 1 to
many relationship so that Access properly displayed the subdatasheet for
all related records.
After upgrading my machine to Access 2003 today, I find that the
subdatasheet is no longer displayed (no "+" symbol.)
I created a new mdb and linked the SQL table in again and set the 1 to
many relationship.

The solution here is to create two queries. you then view the property for
the first query,a nd then set the sub-data sheet as the 2nd query (and,
enter the link master/child settings). This will thus work.

I am not 100% sure why we can't save the settings in the actual table, but
sub datasheets with linked tables can really kill performance.

Anyway...you *can* force this to work if use a query...

 

[Scott]

Ok, not very helpful.
I get really tired when I see some uppity arse make a lame comment like
this.
I was appealing to MVP's for an answer because I did not wish to get a flood
of "ME too" posts from other developers.
The point here is that functionality that was in previous versions now
appears to be buggy and no longer works consistantly in the new version.

BTW - the subdatasheet is the default view provided by Access when a table
with a self join relationship is defined.
I am not trying to create anything special here - just have the
functionality I enjoyed for several years in my development environment.

 

[Duane Hookom]

Slow down. I'm sorry I have an opinion regarding a feature.

We NEVER know how posters use or mis-use features available in Access such
as input masks, lookup fields, captions, sub-datasheets, tables with 255
fields, etc.

If you get upset when people offer opinions then maybe next time you might
try asking something like:
"Please don't give me any opinions about the use of ...feature... as I don't
care what anyone else thinks. I only want to know why ...feature... doesn't
work when I attempt to ...."
Then, I would keep all my opinions/observations about ...feature... to
myself.