Category : Dbase (Clipper, FoxBase, etc) Languages Source Code
Archive   : RRSTUFF.ZIP
Filename : READ.ME

 
Output of file : READ.ME contained in archive : RRSTUFF.ZIP
Dear Registrant:

Thank you for your support of my neat little R&R RRPRINT.DBF file and
supporting utilities. Rather than shareware, I consider this sort of
venture to be a sort of "Bare-Bones" ware. Basically, I put in the grunt
work of creating a .DBF file supporting all of the R&R printers which
are in RRPRINT.CNF which is supplied with R&R Report Writer. This means
that you basically can use this file in conjunction with the R&R Code
Generator, rather than using their klunky .MEM file generator. Personally,
I find it easier to keep track of one file, not 100.

This release contains the following files:

RRPRINT.DBF -- Main printer support database
RRPRINT.NTX -- Index on printer name (GC_PSNAME)
RRFUNS.PRG -- R&R generic functions, along with my own status1()/Status2()
functions
ASSIGN.PRG -- Sample report program demonstrating usage of RRPRINT.DBF
as configuration file
MEMOPS.PRG -- Some neat Scatter/Gather style functions

As you have probably guessed, this package contains no express or implied
warranty. I assume no responsibility, financial or otherwise as to the
fitness of said programs/data. In other words, don't sue me! (You would be
trying to get blood from a stone, believe me!)

Enough of the pseudo legal mumbo jumbo. Basically, I want to thank you
for supporting me by sending me your donation for this utility or
sending me some interesting source utilities. You are probably a fellow
consultant such as myself, and use R&R Report Writer & Code Generator to
quickly turn out "Custom" reports to your users. Now with my RRPRINT.DBF
you can take advantage of adding generic printer support to your application
arsenal.

Note that I have included some samples of how to use my routines. A quick
read through the source code should explain all. Basically, your configuration
routine should have a global printer setting variable (like PRINT_NAME or
something like that). You can use either dBedit() or Achoice() or a similar
function to display a window of printers out of the database file, let your
user select the printer, and assign its name to the global variable
PRINT_NAME. You will then modify an output R&R Code Generator .PRG file
to accept PRINT_NAME as one of its parameters (or just pass it as a global).
Your R&R Report program should open RRPRINT.DBF using RRPRINT.NTX (indexed on
GC_PSNAME) and perform a seek on PRINT_NAME, and assign all of the database
variables to corresponding memory variables. You can use my routines
INITMEM() and STORMEM() to do this automatically and transparently. (Refer
to Memops.PRG)

Adding new print support shouldn't be too much of a hassle. One warning,
however. You should try and write a Clipper based maintenance routine
to maintain the database. I have found dBase and DBXL basically choke on
some of the control character sequences. Clipper doesn't seem to have a
problem with Control characters embedded in database vars. If this file
nets me any kind of $$$ I might be coerced into creating a generic maintenance
routine. Right now my time is kind of krunched, but I would consider it.
I will probably offer a free upgrade to my early supporters, as they are
the people that help you get off the ground with these types of things.

If you have any problems or questions, feel free to E-Mail me at 72117,1632.
Again, thank you for your support, and I hope this little utility saves
you time and energy, and makes you a little more productive.


Darren J. Forcier
Forcier Computer Services





  3 Responses to “Category : Dbase (Clipper, FoxBase, etc) Languages Source Code
Archive   : RRSTUFF.ZIP
Filename : READ.ME

  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/