Subject Re: db 2019 source aliases
From Ken Mayer <dbase@nospam.goldenstag.net>
Date Mon, 31 Aug 2020 06:10:03 -0700
Newsgroups dbase.getting-started

On 8/31/2020 2:15 AM, Edmund Wong wrote:
> Hi,
>
> I've been using dBase 2.6.2 and only just recently upgraded to db2019
> (now that all the WinXP systems are gone).
>
> I tried to open a project(that works under 2.6.2) in dB2019; but
> it errors out:
>
>    Error.  File does not exist.  test.cfm
>
>    File:    testcon.wfm
>    Routine: testConForm::TestConForm
>    Line:    39
>
> On line 39, I have:
>
> class testConForm of TESTCFORM from :kclasses:test.cfm
>
> Now if I remembered, it had something to do with source aliasing.
> However, when I went into my dBase Plus 2.6's source aliasing
> dialog, it's pretty much empty (not a good sign since I do
> recall having something defined).  So I have no settings to
> copy from nor do I remember what I had set.
>
> I added kclasses to the dB2019 source alias, by:
>
>    Alias: kclasses
>    Path: \\srv2\data\forms
>
> That solved that issue; but the system threw another error:
>
>
> Error: File does not exist: basebtns.cc
>
> which points to the following line:
>
>    set procedure to :kclasses:baesbtns.cc additive
>
> This is where I'm confused because basebtns.cc is in the
> \\srv2\data\controls directory and the test.cfm is in the
> srv2\data\forms directory.  Since this arrangement works
> in 2.6.2, and not working in dB2019, are there changes
> in Source Aliasing that I'm missing?
>
> IIRC, I had set for the 2.6.2 application that all
> custom cc belong to the data\controls dir, and
> the forms go to the data\forms.
>
> To add to my confusion, if I'm running the application
> by clicking on the main WFM file in dB2019 ide, am I
> using Source Aliasing or DEO?

Source Code Aliases only work in the IDE. If you upgraded to 2019, then
these do not automatically carry over. You need to go to the Properties
menu in dBASE, and Desktop Properties in the submenu. In the dialog find
Source Aliases, add new aliases there.

DEO is sort of the executable/compiled version of Source Aliases, but in
the executable, source code aliases are ignored. So if you have a
command like:

set procedure to :kclasses:baesbtns.cc additive

The ":kclasses:" part of that statement is ignored by the runtime engine.

DEO is set up in the MyProgram.ini (where "MyProgram" is the name of the
executable), and can be done in the Project Explorer, or manually set
up, and so on.

Ken

--
*Ken Mayer*
Ken's dBASE Page: http://www.goldenstag.net/dbase
The dUFLP: http://www.goldenstag.net/dbase/index.htm#duflp
dBASE Books: http://www.goldenstag.net/dbase/Books/dBASEBooks.htm
dBASE Tutorial: http://www.goldenstag.net/dbase/Tutorial/00_Preface.htm