prosit
asked on
Access 'nested' tables?
Hi,
I am in the process of converting an access database and code to SQL and while copying tables into SQL I stumbled over something weird.
I know access reasonably well, but had not seen this before, please help.
On the enclosed picture there's a table called PO_Total which is a linked table to another access database. However when I open it there a 'drop-down' + next to each row with more data... where is that coming from, and where is that defined?
Thank you in advance, please ask any questions if this does not make sense...
~J
delete.png
I am in the process of converting an access database and code to SQL and while copying tables into SQL I stumbled over something weird.
I know access reasonably well, but had not seen this before, please help.
On the enclosed picture there's a table called PO_Total which is a linked table to another access database. However when I open it there a 'drop-down' + next to each row with more data... where is that coming from, and where is that defined?
Thank you in advance, please ask any questions if this does not make sense...
~J
delete.png
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ahh, confusing me while trying to give me more than I asked for ;)
Thanks guys...
~j
Thanks guys...
~j
It is a UI feature in the tables--not a place where you usually want UI to be.
When enabled, any table that is the 'one' in a one-to-many relationship will show a subdatasheet for the 'many' side.
This is strictly a UI feature. If can be ignored if the purpose is to migrate the data away from Access.
If the database file will continue to be used, it can become a performance issue.
Many professional developers will turn this off.
It can be done table by table through the Access UI (although I have forgotten how now)
Or by code.
the VBA code I used to identify tables that had this feature was
Open in new window
From there it was simple after checking that I wasn't going to hose anything up to change
MsgBox tdf.Name
to
tdf.Properties(conPropName
and turn it all off.