[AccessD] OT Colby's Framework

John,
Reply and questions inline below,
/borge

----- Original Message ----- 
From: "John Colby" <jwcolby at colbyconsulting.com>
Subject: Re: [AccessD] OT Colby's Framework


> One quick question, did you work
> through all the articles or are you jumping in at the end?  I don't care,
if
> you know what you are doing and are jumping in that is cool, I'm just
> curious.  If you worked through all the articles and the example code then
I
> am absolutely floored at your persistence.  This stuff is not necessarily
> easy.

I am jumping in at the [deep] end!
I have been stepping through your code a few times, and hopefully learnt a
bit.

My knowledge and experience with class modules, objects, eventsinking etc.
is minimal.

> As for your problem, the framework is looking for a sysvar called
> "EnblPtrStack", which should be true or false.  I use SysVars to turn
on/off
> functionality in my framework, and this code is telling the cIS class to
> either use the class logging mechanism or do not use it.  The class
logging
> mechanism is a class which tracks the names of the classes as they are
> instantiated, so that you can get a listing in instantiation order of all
> the class instances currently loaded.

In your table "usystblFWSysVars " in the MDA code library your have the two
sysvar records:
53 EnblPtrStack
54 EnblNameStack

In the Init() code of the clsInstanceStack the corresponding two variables
blnEnblPtrStack and blnEnblNameStack are set to True by default.

So while initializing the Framework Class Logging is On by default.
Then you can have it turned on or off. Right?

Now, why would you want to turn it off?
Reading your article I was under the impression that the Class Logging
feature is essential to a proper managed termination procedure?


> I also have to say that "it is not failing here".  I just opened the zip
> file, unzipped it and relinked FE to BE, and it runs perfectly, at least
> until you try and close the database, whereupon the module in the
> usysFrmFWCleanup in the framework throws a runtime error.  There is a me.
> Code fragment in the form_Close.  Sigh.  I have fixed that and will upload
> the zip to my site.

After your reply I unzipped a 'fresh' version of your demo.
Runs smoothly - no problem (Yes, I deleted the Me. code fragment)

Last week I had problems with the MDAC and had to install latest version of
MDAC for several things to function properly.

While having the corrupt MDA  on my system I had changed the

        Set mfwcnn = CodeProject.Connection
to read
        Set mfwcnn = CurrentProject.Connection
because my Help would'nt recognize CodeProject ,
...and I was just mocking around in the dark.

This was the reason for my demo version falling over.
I had of course forgotten about this "minor" change in the code.

Questions:
So, Codeproject in this instance refers to your C2DbFW3G.MDA code library.
I guess this link is established when you set up the MDA in the References??

General question: Can you have more than one MDA linked to your FrontEnd?
If so, what is CodeProject then referring to? The first instance of MDAs in
the Reference List?

For your demo purpose why do you have the usystblFWSysVars both in the MDA
and in the FrontEnd?
It doesn't appear that the table in the FrontEnd is used.
If it was to be used, I assume it would be to demonstrate the 'over ride'
facility of the SysVar values as they exist in a particular FrontEnd.

If that is the case, am I correct in assuming that the usystblFWSysVars
table in the FrontEnd woud be read and dealt with in the same manner as the
tables
usystblAppCont
usystblFWSysVars

by running similar code as
        fw.SVAPPContInit "usystblAppCont"
        fw.SVAPPDataInit "usystblAppData"

with the necessary functions established in the clsFramework?

Or am I missing something?

/borge