RAP Activation in EndUser
Certainly feeling pretty helpless after a few years off.
My reports need to use RAP. So the CALC tab is showing up just fine in the
Designer. Also all the Tool boxes, Objects and so forth.
However, when selecting an EVENT on which to write CODE, no "procedure ..."
shows up in the CODE pane.
I try to type in the code pane, and just get beeps.
However, can drag statements into the code pane, and they display fine.
Then, of course a "compiler" error is reported, so I can only assume that
the RAP thinks there
is something in the CODE pane to compile, and the Event is marked with a RED
marker.
The ppDesigner is connected to a Explorer, and the reports are pulled out of
a database.
Other Info
All the Designer.RAPOptions := [TRUE];
raIDE is included and used.
Version 9.02 ENT
The DEMO RAP program works fine, and can edit RAP. after I compile, so I
assume my installation is good.
Any clues ?
Phil.
PS - Thks for support in pipeline forum.
My reports need to use RAP. So the CALC tab is showing up just fine in the
Designer. Also all the Tool boxes, Objects and so forth.
However, when selecting an EVENT on which to write CODE, no "procedure ..."
shows up in the CODE pane.
I try to type in the code pane, and just get beeps.
However, can drag statements into the code pane, and they display fine.
Then, of course a "compiler" error is reported, so I can only assume that
the RAP thinks there
is something in the CODE pane to compile, and the Event is marked with a RED
marker.
The ppDesigner is connected to a Explorer, and the reports are pulled out of
a database.
Other Info
All the Designer.RAPOptions := [TRUE];
raIDE is included and used.
Version 9.02 ENT
The DEMO RAP program works fine, and can edit RAP. after I compile, so I
assume my installation is good.
Any clues ?
Phil.
PS - Thks for support in pipeline forum.
This discussion has been closed.
Comments
The ReportBuilder Developers and RAP.hlp contain information on using an
configuring RAP. There is also a new Learning ReportBuilder RAP tutorial.
(see the Download section of our web site).
There Calc tab offers 3 different views of the RAP CodeModule: Variables,
Events, and Module. These are explained in the documentation. The Variable
view is simple view that does not show the procedure declaration - it only
shows the body. Perhaps that is what you are seeing.
--
Nard Moseley
Digital Metaphors Corporation
http://www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
A couple of things:
TO refresh my memory, I am working on an older application. This has many
complex reports, which are stored in a End User database, and accessed
primarly thru the ppExplorer.
So, these reports and application was built using RB 5.0 ENT. I assume they
have been converted to RB 9.02 automatically.
To isolate this problem, I have written a smaller TestHarness, which simply
invokes a ppDesigner connected to the ADO connection to my database.
If I write a FRESH report, and save it to a file, the problem with the Code
Editor does not appear to occur.
So, at this point, I can only assume the issue is with the RB 5.0 to RB 9.02
conversion,
OR
With the invokation of the Designer from the Explorer.
The CodeEditor will also lock up sometimes by typing in the GREY area after
a CONST declaration
and making a syntax error in the GREY area, compiling. This is a complex
series of actions.
Phil
Have not heard of this issue before.
If you are using the BDE, make sure the setting for MaxBlobSize is large
enough to load the reports correctly.
Also, make sure that you do not have a corrup installation. See article
below...
--------------------------------------------
Article: Cleaning up a Corrupt Installation
--------------------------------------------
If you have been advised by Digital Metaphors technical support that you may
have a corrupt installation, or if you are having difficulty installing,
compiling or running applications after a ReportBuilder install, then it may
be necessary to manually remove all ReportBuilder files from your system.
Corrupt installations usually result when you are installing over a previous
version of ReportBuilder which was not installed into the default directory,
which was recompiled from the source, or when ReportBuilder files were
manually moved from the default install location. Cleaning up a corrupt
installation, consists of locating all ReportBuilder related files, and
deleting them from your system. The first step is to use the uninstall
program to remove as much of ReportBuilder as possible.
Run the uninstall program
1. Exit Delphi, and all other applications. You should have no applications
running except the uninstall, otherwise you may lose some of your work.
2. Select Start | Settings | Control Panel from your Windows desktop.
3. Double-click the Add/Remove programs icon.
4. Locate the version of ReportBuilder you wish uninstall and double-click
it.
5. The first page of the Uninstall Wizard allows you to choose between an
Automatic or Custom uninstall. Choose Custom and click the Next button.
6. Click the Select All button, then the Next button. Repeat these steps
until you reach the last page of the wizard.
7. Click the Finish button. All of the items you selected will be removed
from the system.
8. After all the ReportBuilder files are removed, you may be prompted to
reboot the system. If this is the case, reboot the system.
Delete the ReportBuilder root directory (and all subdirectories)
1. Using the Windows Explorer, locate the ReportBuilder root directory. The
default directory is:
C:\Program Files\Borland\DelphiX\RBuilder
2. Once you have located this directory, inspect it. If you have any custom
work in this directory which you would like to keep, move it to another
directory.
3. Delete the ReportBuilder root directory.
Delete all remaining ReportBuilder files
1. Using the Windows Explorer, search the entire hard drive for all
occurrences of:
dclRB*.bpl
dclRB*.dcp
rb*.bpl
rb*.dcp
2. Delete any occurrences which correspond to the version you are removing.
All packages are named with the convention NN, where the first number
is the ReportBuilder version and the second number is the Delphi version.
Thus, a typical package name for Delphi 5 would be rbRCL45.bpl. The same
package for Delphi 4 would be: rbRCL44.bpl. Check Installing ReportBuilder
for a list of the packages associated with each version.
3. Using the Windows Explorer, search your hard drive for all occurrences
of:
pp*.*
da*.*
ra*.*
4. These are the prefixes used by individual ReportBuilder units. 'pp' is
used for ReportBuilder units, 'da' is used for DADE units, and 'ra' is used
for RAP units. Depending on which ReportBuilder you have (Standard,
Professional or Enterprise) you may not have all of these unit types.
Additional Notes
1. Never have Delphi running when installing ReportBuilder.
2. All ReportBuilder related files should be stored in the root directory
$(DELPHI)\RBuilder.
3. All ReportBuilder run-time packages should be stored in the
Windows\System directory.
4. You should never have ReportBuilder files in Delphi\Lib, Delphi\Bin or
Delphi\Projects\Bpl.
--
Tech Support mailto:support@digital-metaphors.com
Digital Metaphors http://www.digital-metaphors.com
--
Nard Moseley
Digital Metaphors Corporation
http://www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com