Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Subclassing DataEnvironments
Message
From
17/10/2000 16:57:39
Gerald McKinsey
Keystone Consulting Services, Inc.
Yorktown, Indiana, United States
 
General information
Forum:
Visual FoxPro
Category:
The Mere Mortals Framework
Miscellaneous
Thread ID:
00429334
Message ID:
00430577
Views:
12
> Here's what I recommend:
>1. Create your own "Common" library (maybe staring with a "D"ustin <s>)
>
>2. Create a subclass of CDataEnvironment (let's call it "DustinEnvironment") and store it in your common library
>
>3. Subclass each project's "main" data environment (created automatically by QuickStart) from "DustinEnvironment". Its "cDefaultDatabaseName" property specifies the name of the application's default database. The main data environment is given the name of your database plus the suffix "Environment" (for example, ProjMgrEnvironment).
>
>4. Create all other subclasses from your project's main environment.

Kevin,

This is exactly what we did. We didn't want to change the foundation, so subclassed your cDataEnvironment into one of our main KeyLibraries. (Similar to where you told us to put the subclassed "kBizObj")

In your step 3, you mentioned something about the Project's Main DataEnvironment being automatically being created by QuickStart. You didn't actually say it, but did you mean DELETE the Project's Main Data Environment, and then make a new one from Subclassing the DustinEnvironment?

Instead of deleting, we used "Redefine Parent" in the Class Browser on the Project's Main DataEnvironment to change its parentclass to DustinEnvironment.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform