If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#20
|
|||
|
|||
How to enforce subtypes/supertypes in Access 2000?
It sounds like you're using Access 2000, which does not have this option.
(This would also explain why your VBA references were set to ADO by default, and not DAO) You don't want SQL-92 anyway, if you are working with a Jet database. -- Cheers, Graham Mandeno [Access MVP] Auckland, New Zealand "Bob" wrote in message ... Hi Graham, Actually I did have another question too - more out of curiosity than anything else. You mentioned earlier that to switch to ANSI-92 mode you need to go to Tools Options Tables/Queries. When I following these directions I get a form with a Table and a Query design section. In the Table design section, I get options to change the default field sizes, the default field type, and a box for "AutoIndex on Import/Create". In the Query design section, I get checkboxes to "show table names", "output all fields" and "enable autojoin". I also get radio buttons to "Run permissions" as "Owner's" or "User's". But I don't see anything that refers to ANSI mode. Any ideas why? Regards Bob "Bob" wrote in message ... Whoo Hoo! Thanks alot Graham. It's finally working. :-) Just one more question though, why do you prefer DAO over ADO? I've now acquired a copy of the "Microsoft Office Access 2003 Bible" and there's a small section in it that asserts that ADO is to be preferred over DAO because Microsoft does not plan to provide any future enhancements for the latter. I'm still starting out at this, so I'm not entirely clear on the other pros and cons of each. Regards Bob |
Thread Tools | |
Display Modes | |
|
|