A
Access_Misfit
(Yup, first-time poster here. Ill try my best not to embarass myself)
OK, the thing is this. I need to get a list of the tables/queries/reports
within a just-delivered Access2002 file from within my MFC code (utilizing
MSA-ODBC). I get dozens of these files a day.
Ive got my MFC code tuned perfectly to do what I need, but there is a series
of keystrokes that
still haunts my brain.
*EVERY* MDB file sent to me has the MSysObjects table protected (by default)
from [ ]READ access.
In every file I have to go thru the steps of making the [X]SysObjects
visible, then Security->Modify
MSysObjects [X]Read-able, (and then I turn [ ]SysObjects visibility back off).
.. *THEN* I close
the whole sh'bang, and my software does its magic perfectlty... This single
sequence of menu
ops makes me want to go home and kick my dog every night.
My questions are...
A) Is there any way (via puting some ODBC flags into the connect string - or
some such)
whereby I can bypass this irritating manual sequence?
B) Is there any way I can define (on the fly, via my MFCcode via ODBC) some
query which will
accomplish the same thing? (a backdoor?)
C) Is there any way I can define (on the fly, via my MFCcode via ODBC) some
MACRO which will
unlock the MSysObjects table and make it readable via ODBC
D) Is there *ALREADY* some ODBC function I have overlooked which is designed
to do just what
I need (am I re-iniventing the wheel here?).
E) And if none of the above can bring me joy, is there any way a MACRO that I
can put onto
a personal MACRO toolbar can do the steps via a single-click of a button?
(so that the macro is stored on my local harddrive, and not within the MDB
file, and will show up on
my toolbar anyway whenever I open a new MDB file)
Help me Obi-Access-Kenobi. You're my only hope!
-Dave
davidjaybrown(at)engineer.com
OK, the thing is this. I need to get a list of the tables/queries/reports
within a just-delivered Access2002 file from within my MFC code (utilizing
MSA-ODBC). I get dozens of these files a day.
Ive got my MFC code tuned perfectly to do what I need, but there is a series
of keystrokes that
still haunts my brain.
*EVERY* MDB file sent to me has the MSysObjects table protected (by default)
from [ ]READ access.
In every file I have to go thru the steps of making the [X]SysObjects
visible, then Security->Modify
MSysObjects [X]Read-able, (and then I turn [ ]SysObjects visibility back off).
.. *THEN* I close
the whole sh'bang, and my software does its magic perfectlty... This single
sequence of menu
ops makes me want to go home and kick my dog every night.
My questions are...
A) Is there any way (via puting some ODBC flags into the connect string - or
some such)
whereby I can bypass this irritating manual sequence?
B) Is there any way I can define (on the fly, via my MFCcode via ODBC) some
query which will
accomplish the same thing? (a backdoor?)
C) Is there any way I can define (on the fly, via my MFCcode via ODBC) some
MACRO which will
unlock the MSysObjects table and make it readable via ODBC
D) Is there *ALREADY* some ODBC function I have overlooked which is designed
to do just what
I need (am I re-iniventing the wheel here?).
E) And if none of the above can bring me joy, is there any way a MACRO that I
can put onto
a personal MACRO toolbar can do the steps via a single-click of a button?
(so that the macro is stored on my local harddrive, and not within the MDB
file, and will show up on
my toolbar anyway whenever I open a new MDB file)
Help me Obi-Access-Kenobi. You're my only hope!
-Dave
davidjaybrown(at)engineer.com