At 11:30 PM 12/17/2004 -0500, Bob Castanaro wrote:
.... So if I got this right, there is just some sort of pointer in file 2 showing
where the rtf is in file 4. If I get data corruption in file 2 like a broken row
pointer, and fix it with rscope, that RTF data may not be been affected at
all. If that is the case, I am one happy guy. We never had this functonality
before v7. I am just so very wary of note fields after being burnt alive with
bad backups.
Bob,
You'll have no problem storing RTF data in VARCHAR field.
If you reach the 2GB limit of 7.1/7.5, you can easily migrate to R:BASE V-8 Turbo with NO LIMITS. (There are no hard drives available that break the limit of V-8 Turbo.)
Also, did you know that you can keep all those RTF files outside the database in a secure directory, referenced and/or indexed by your R:BASE 7.x/8.0 Application. You can manage the updates, etc. by simply using RBBE command also supported in EEP and Custom EEPs.
Example:
RBBE YourRTFFileSomeWhere.RTF
This will bring up that file in "Built-In" RBG7 RTF Editor to manage your file with following features:
. Print . Copy . Cut . Paste . Undo . Fonts . Search . Search/Replace . Fonts/Font Size . Bold . Italic . Underline . Left Align . Center . Right Align . Bullets
You are also able to load RTF from an external file or even save to external file.
Enjoy the unbounded possibilities and make sure to have fun!
Very Best R:egards,
Razzak.
