Recent content by DamoDiggler

Ok, thanks I can appreciate this is not the most efficient way of doing it, but it's all we have at this time, so I have to persevere, in future I can rework all of this, but right now I'm trying to make it work... the complete DB back end size is 14mb, so I don't think it's going to hurt too...

Yes, I even tried removing the front end 'tblProducts' and re-added/linked to it from the back end 'tblProducts', but still the front is not mirroring that SubTable as, hopefully, you can see in the attached images.

Ok, so I zipped the photos and attached them to this message.

You mean, as in via the Relationship Manager?! ... yes, I have created the same 'one-to-many' link as I have in the tables that do display correctly. :confused:

Thanks DBguy, Even though this does perform fine on the back end?! .. it's the front end the SubDataSheet is missing from... but, in response to your question, I don't have either of those options in 'design view' (front or back), but then again... those particular options are also absent from...

Thanks CJ, I have removed the offending table and re-added the dependents as 'structure' only... but again, the front end persists to avoid the attempts to add it in as a 'SubDataSet', which appears to be the thing that everyone appears to be suggesting here hahah, so "Leave it!" they say haha...

Thanks isladogs, Yes you're right about the correct terminology, they are indeed 'Linked' tables on my front end referencing the tables on the back end. The missing datasheet is stored on the back end, as are all the others that are 'Linked' on the front-end. So, the missing SubDataSheet is...

Hello! I have a strange anomaly with one of my tables I was hoping to get some insight on... I have at least 3 different shared (as in linked) tables, that (when open) feature the + symbol on the left hand side.. indicating a SubTable is available, yet on this 'anomaly' state I have with a new...