Dear FRB customers,
FRB version 3.10 released and available for download from
http://www.fomintools.com/update.htm
This is Clarion 7.0 compliant release.
The most notable change is the new FRB libraries file names for Clarion 6.
Old file names in version 3.09 where:
Clarion6\Bin\C6FRBX.DLL
Clarion6\Lib\C6FRBX.LIB
Clarion6\Lib\C6FRBXL.LIB
New file names in version 3.10 are:
Clarion6\Bin\C60FRBX.DLL
Clarion6\Lib\C60FRBX.LIB
Clarion6\Lib\C60FRBXL.LIB
So, please, don't forget to uninstall previous FRB version before installing FRB
3.10. If necessary, please, change your installation scripts to deliver new
libraries to your customers.
Below you can find quoted my news posting with explaination of this change.
Thank you,
---
Oleg Fomin <oleg@fomin.info>
"Oleg Fomin" <oleg@fomin.info> wrote:
news:A921.1189430061.3190@discuss.softvelocity.com...
> Hi Guys.
>
> I sure, everybody has taken a look at the nice blog written by Gary James at
> http://www.strategyonline.co.za/blog/index.php/?p=543
>
> IMHO, the most annoying thing in this instruction is the last step (quoted
> below).
>
> > Step 15. One hurdle to go.. The last things to deal with is that this
> example was built using Clarion 6, but you're compiling it using Clarion 7..
> Under the "Libraries, Objects and Resource Files" list (pictured here), you'll
> see a file called "C60JSpellX.LIB". This is the J-Spell library for Clarion
> 6. You'll need to remove that (right-click, remove) and add the Clarion 7
> library instead, i.e. "[Clarion 7]\Accessory\Lib\C70JSpell.LIB".
>
> As you can guess from the subject, now you can bypass this step while
> compiling Fomin Report Builder (FRB) examples. The trick is that I have
> slightly changed FRB templates in product version 3.10. The change consists
> of the following template code.
>
> #SET(%ValueConstruct,'C%V%FRB%X%%L%.LIB')
> #PROJECT(%ValueConstruct)
>
> As a result, in the project tree (Library, Objects and Resource Files)
> you'll be able to find such a tricky LIB file name:
>
> C%V%FRB%X%%L%.LIB
>
> This library file name uses following project system macros - %V%, %X% and
> %L%. Actually, at the compile time Clarion project system will make use of
> one of the following libraries (depending from the Clarion version and
> Local/Standalone switch):
> C55FRBX.LIB
> C55FRBXL.LIB
> C60FRBX.LIB
> C60FRBXL.LIB
> C70FRB.LIB
> C70FRBL.LIB
>
> Now you know the meaning of this tricky "percent" library name. And, please,
> click [No] button when you'll be prompted with the following message: "The
> project links in the library "C%V%FRB%X%%L%". Is there a matching
> project/application file that creates this library?".
>
> Of course, there is a project for the library, "but it's here on my
> computer, protected by man-eating rottweilers." (C) Gary James ;-)
>
> As a conclusion, I want to say that such usage of project macros isn't my
> patented "know how". Quite the contrary, this is a common feature documented
> at the Project System Reference. Moreover, this can be a C7 compliance
> standard for all the Third-Party suppliers. I think, the benefit for our
> customers is quite obvious.
>
> Thank you,
> ---
> Oleg Fomin <oleg@fomin.info>
> http://www.FominTools.com for Clarion developers
|