John Colby
jcolby at colbyconsulting.com
Wed Jul 2 07:00:50 CDT 2003
And it simply makes no sense, particularly if I can simply parse the SQL string from the query def to get the field names. I'll get back to you on that one. John W. Colby www.colbyconsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Gustav Brock Sent: Wednesday, July 02, 2003 7:51 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] weird query def Hi John Yes, that may be an "illegal" trick. However, it should be possible to dynamically add/remove a reference to the foreign mdb, but I'm not sure how reliable that would be. /gustav > Gustav, > The code he sent was an ado version of what you were doing (more or less). > The reason he sent it off list is that it was two dbs as attachments which > of course don't go to the list. However AFAICT the reason it worked is that > he referenced the main FE from what will be the library and that is > unfortunately illegal - if not literally, at least in practice. Referencing > the FE allowed the wizard to "see" the function that the query in the FE was > trying to execute, at least that's my take on it. > The wizard needs to be available from any of one or many different > applications at once so to reference all of those apps simply doesn't make > sense. > John W. Colby > www.colbyconsulting.com > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Gustav Brock > Sent: Wednesday, July 02, 2003 2:14 AM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] weird query def > Hi Mark and John > Hey, nice couple you two! Thanks for the insight. > /gustav >> sent it off-list >> Mark >> could you send me the code? >> John W. Colby >> Not sure if this is any help, but I just tried it using ADO with the >> function, query and table in db1 and the code for getting the field >> names from an adodb.recordset in db2 (which also referenced db1). Worked >> fine... >> Mark _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com