 The
Basic Scenario – Our Files DLL is split up into a Files DLL and a Classes
DLL.
|
|
| For this scenario I picked the School dictionary from the Clarion 4
examples. To begin I’m going to create the lowest level DLL in my application.
For this I want to export only Classes and all Globals. |
 |
| For this first app I’m going to build it 32 bit, because there are
too many classes to compile this in 16 bit. You will notice that there
is no dictionary specified because the app will only export classes. The
first thing we want to do is go to the project settings and set the Target
OS in the Global options to 32 bit. |
 |
| Next we’ll turn to the Global properties for the application. Since
this is the base level of the app as far as our DLL calling tree is concerned,
we will leave Generate template globals and ABC’s as EXTERNAL unchecked
for this DLL. |
 |
| Next we’ll add our global extension template for the ABC DLL Toolkit,
the ABC Data/Class DLL Toolkit extension. If we go to the Exports tab,
we can select whether to export classes or files from this Application.
For this app, we’ll simply check everything in the Classes box and go on. |
 |
| That’s all we need to set up for this app, now just make the app and
we’re ready to move on to the Files app. We set this one up similarly to
the ABC lib except here we obviously need to specify a dictionary. |
 |
| The first thing I do, again, is to go to the project setting and set
the Target OS to 32 bit. If I don’t do it first, I inevitably forget and
wind up with link errors. Before I go to the Global settings I will add
the Lib for our ABC classes to the project. This is an important
step and easy to forget as well because the app will compile and link Ok
if you do not include the ABC Lib, but it will cause your app to GPF the
first time you try to access a method of the Filemanager class. |
 |
  |
| This should result in a module view like this: |
 |
|
|