VERSIONS: Paradox 9 Runtime
SUBJECT: Using Application Framework applications developed with Paradox 9 SP4 in Paradox 9 Runtime SP3.
BY: ALLEN MULVEY
Date: 17 October 2000
I recently upgraded Paradox from v8 to v9 including the runtime. To my surprise only one of several applications using the Application
Framework would run under Paradox 9RT SP3, all ran fine under the full version SP4. Upon checking to find out what was different I noticed that
I had three different file sizes for the appName.ssl file which the framework uses to initialize the application. The application that ran had a file
size of 48k the others were either 47k or 49k. I copied the 48k file over the others (after backing up the original, of course) and everything started
working.
Apparently applications developed under v8 have a file size of 47k. version 9SP3 has 48k and version 9SP4 has 49k appName.ssl files. *Only*
the SP3 version will work in Paradox 9RT SP3. There are also different file sizes on the appName.exe files but either the SP3 or SP4 versions *seem*
to work.
On my machine these files are located in the following folder:
c:\Program Files\Corel\WordPerfect Office 2000\Paradox\frmwrk\exe
As there will apparently be no SP4 for the runtime I copied the SP3 version of this file into my framework setup folder so that future
applications will function under the runtime.
Just a little followup - as you might expect, if you use the SP3 ssl file you must also use the SP3 exe file. If these files are mismatched the
printing routines do not properly initialize and weird things happen.
Sometimes you can print and sometimes you can't.
VERSIONS: Paradox 10 and later
SUBJECT: Converting Paradox 8 and 9 FrameWork Applications to Paradox 10
BY: Frank < rsdATsbcglobal.net >
Date: 5 June 2002
If anybody else out there has the same situation here was the fastest fix I could find and so far through "limited testing" it appears to
work.
- Remove all the code AF put in every event in page 1 of every form it created (make sure your developer's pref. are set to advanced to see them
all). When you created a new form in AF mode, AF put code in every event initializing and opening these .ldl libraries and then calling routines
within these libraries. Fortunately from what I can see so for, most of the routines these .ldl libraries stored have no effect on the application when
it runs. The only thing I have found so far is the behavior in every field with a right mouse click. The AF default is a Cut, copy, paste, locate, locate
next and apparently this is some global behavior loaded in the one the .ldl libraries because there is nothing in the 3 .lsl libraries I can see. When I
removed this code and run the app the right mouse click (other than objects I have built my own code on for this) give the standard Paradox 8 Cut,
copy, paste, filter.
- Edit the SSL that the AF makes and remove the references that open or init these .ldl libraries. I had modified this to initialize other alias' from
an .ini file and open and initilize my own libraries.
- Of course save and recompile these forms and libraries.
- Create a new or use the glib library or main library that are both .lsl and add what you need for menus (my app already was set up to use it's
own menus, form sizes, colors, etc.) If you do not have your own menus the AF needs the .ldl to create the menus that the AF builds automatically.
From what I can see if your app ran in the project viewer and you opened anything, AF would go to the appprob table to get the menu, color, size,
etc. I am assuming it did this because of something in these ldl that told it to. It doesn't use these settings when anything is opened using
code.
Bottom line is what I found is there is very little you have to build yourself. It was a little trial and error to follow the errors as the App and
then forms were opened and track down what needed to be added. Of course I didn't make extensive use of libraries back then because I didn't
know how and possibly I have code added that duplicated some of the things these .ldl did???
As the ".exe" file that AF creates, yes I know what it did. In fact this was what has caused me the problems in the first place as Win2000 will
not execute it. While I am recompiling everything into Paradox 10 right now, a short term solution was just changing the startup icon properties
from this .exe file to the ssl file. Everything seems to work.