C
ctyrrell
I have created a library of generic routines I use for several of my
Access appplications, MyLib.mde. I just create a reference to it from
the Access Application and I can use all the routines and globals from
the App.mdb as I develop it. As I am developing code in the App.mdb,
the intellisense works beautifully, up to a point. Once I have typed
the name of the routine, intellisense shows me what arguments I need to
pass, and their types, etc. So far so good.
What I don't like however, is that the case of the routines (in my
typing) does not automatically fix itself, once I have completed the
statement and, if I have any other uses of that same routine (or
global), they all change to the case of what I am typing. This makes my
code in the App.mdb much less readable, and is annoying.
For a very simple example, I have a global gfDebug in MyLib.mde, that I
use throughout my code in both MyLib.mde and App.mdb. When I type
'x.visible = gfdebug', I expect it to automatically become 'x.Visible =
gfDebug', but it does not. Instead I get 'x.Visible = gfdebug'. And
everywhere in the App.mdb that I use gfDebug now becomes gfdebug. Note
that the 'v' of visible, does update to 'V', as expected.
I usually count on the case of my typing automatically correcting, as I
go along, so that I am sure I typed the variable or routine name
correctly.
This is not a show stopper but it is my only problem with my Access
library paradigm. Is there anything I can do to make it behave the way
I would like?
Any insights or feedback would be greatly appreciated. By the way, I am
using Access 2000.
Thanks,
Christine
Access appplications, MyLib.mde. I just create a reference to it from
the Access Application and I can use all the routines and globals from
the App.mdb as I develop it. As I am developing code in the App.mdb,
the intellisense works beautifully, up to a point. Once I have typed
the name of the routine, intellisense shows me what arguments I need to
pass, and their types, etc. So far so good.
What I don't like however, is that the case of the routines (in my
typing) does not automatically fix itself, once I have completed the
statement and, if I have any other uses of that same routine (or
global), they all change to the case of what I am typing. This makes my
code in the App.mdb much less readable, and is annoying.
For a very simple example, I have a global gfDebug in MyLib.mde, that I
use throughout my code in both MyLib.mde and App.mdb. When I type
'x.visible = gfdebug', I expect it to automatically become 'x.Visible =
gfDebug', but it does not. Instead I get 'x.Visible = gfdebug'. And
everywhere in the App.mdb that I use gfDebug now becomes gfdebug. Note
that the 'v' of visible, does update to 'V', as expected.
I usually count on the case of my typing automatically correcting, as I
go along, so that I am sure I typed the variable or routine name
correctly.
This is not a show stopper but it is my only problem with my Access
library paradigm. Is there anything I can do to make it behave the way
I would like?
Any insights or feedback would be greatly appreciated. By the way, I am
using Access 2000.
Thanks,
Christine