Category : Paradox DBMS
Archive   : TECH91.ZIP
Filename : TI667.ASC

 
Output of file : TI667.ASC contained in archive : TECH91.ZIP







PRODUCT : Paradox NUMBER : 667
VERSION : 3.xx
OS : DOS
DATE : September 11, 1991 PAGE : 1/1

TITLE : Using Look-up Tables in PPROG & Paradox Runtime




When using RUNTIME to run an application created with the
Personal Programmer, any Look-up tables being used do not appear
on the screen when pressing .

To enable this you must make a change in the code that is created
by PPROG:

There is a section of code within the edit or data entry
module that uses a WAIT TABLE...UNTIL "F1"... You need to
remove the "F1". Here is what to do:

1) Play your application with Paradox.

2) When you get to the spot where the Look-up should be,
press .

3) Press to end the edit. You will see the Cancel
Debug menu.

4) Choose {Debug}, then press to edit the script.

5) You will be taken to the AppNameUTL script and the
section that contains the WAIT. Delete the part that
says "F1", (ie: delete the F1 its quotes and following
comma).

6) Be sure you leave the rest of the code intact (it will
say UNTIL "F2","F7" etc).

7) Press to save the script.

8) Play the AppNameLIB script to rebuild the libraries.
Where AppName stands for the name of your application.

This will need to be done for every different action defined, not
for every Look-up. In other words, if this Look-up was in an
edit session, this will fix all look-ups occurring within an
edit. If you also have a data entry or add session in your
application that uses a table lookup, you will have to repeat
this for one of the data entry and/or add Look-ups. If your
application is modified you will have to repeat this procedure.










  3 Responses to “Category : Paradox DBMS
Archive   : TECH91.ZIP
Filename : TI667.ASC

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/