My "makeform" and "makereport" routines go back to 6.5 (maybe even before 
that).  I just modify the routine if needed when versions are upgraded for 
system table names.  Back in 6.5 days there wasn't a way to unload forms & 
reports from a menu.  To me, this routine is easier because all I have to do is 
type in the form/report name, I don't have to move it anywhere.  I keep 
thinking that I should put up a menu of forms/reports so I don't have to type 
it, I can just pick it from the menu.
I would never move form/report files to the production database directory.  If 
you do, then you either have to erase them when you're done or you live with 
the clutter of having all those files in the live directory.  My OCD won't 
handle that.
So in my case, I always have a directory somewhere else that my routine saves 
the files to.  I can either erase everything out of there if I want, or you 
keep those files in there forever and you always have a "record" of 
forms/reports sent over and can restore from there if you need a backup.  

So in my testing development I type:  RUN MAKEFORMIn live I type:  RUN 
C:\TEMP\TEMPF\FORMNAME.FRM
And I am usually developing forms/reports here in my office and then need to 
transfer those files up to the client.  So I transfer over today's files up, 
and then do the "run" from the client's site.


Karen



    On Tuesday, February 18, 2025 at 08:15:25 AM CST, Larry Nemetz 
<[email protected]> wrote:   

 
I may be naive but why not go into the Database explorer and UNLOAD the report
 
from the test database which will get you the two files.
 
Then copy the files to the active folder for your production database.
 
Open the database and then in Database explorer LOAD the report???
 
  
 
Larry Nemetz, DVM
 
The BIRD Clinic Veterinary Corp
 
200 S Tustin St, #E
 
Orange, CA 92866
 
(714) 633-2910
 
[email protected]
 
  
 
From: 'Karen Tellef' via RBASE-L <[email protected]>
Sent: Saturday, February 15, 2025 1:09 PM
To: [email protected]
Subject: Re: [RBASE-L] - 6.5++ WIndows
 
  
 
Not sure if this'll help, Ron, but I had created this routine for 6.5 windows 
that I would use to create my report files.  It does look like your syntax 
(altho I use "#1" instead of the long column name).  Try copying this code into 
a program file and run it?   Obviously change my hard-coded directory
 
  
 
  
 
SET VAR vformname TEXT = NULL
SET VAR vfilename TEXT = NULL
set null -0-

WHILE 1 = 1 THEN
  SET VAR vformname = NULL, vfilename = NULL
  DIALOG 'Enter WINDOWS report name:' vformname vendkey 1
  IF vformname IS NULL THEN
    BREAK
  ENDIF

  SET VAR vText = (SGET(.vformname,8,1))
  SET VAR vfilename = ('c:\temp\tempf\' + .vText + '.REP')
  DIALOG 'Enter filename:' vfilename vendkey 1
  IF vfilename IS NULL THEN
    BREAK
  ENDIF

  OUTPUT .vfilename
  WRITE 'DROP REPORT', .vformname
  UNLOAD DATA FOR SYS_REPORTS2 WHERE #1 = .vformname
  OUTPUT SCREEN

  TYPE .vfilename

  pause

ENDWHILE

dir c:\temp\tempf
 
  
 
  
 
Karen
 
  
 
  
 
On Saturday, February 15, 2025 at 12:47:48 PM CST, Ronald C Peterson 
<[email protected]> wrote:
 
  
 
  
 
How can I move a report from my test database into a production database. 
 
  
 
Here is the routine I run:
 
  
 
OUTPUT "reportname".rpt
 
write "delete rows from SYS_REPORTS2 whe sys_report_name = ""reportname"""
 
---This will delete the old report if there was one.
 
unload data from SYS_REPORTS2 WHE SYS_REPORT_NAME = "reportname"
 
OUTPUT SCREEN
 
  
 
This creates both the "reportname.rpt" and "reportname.lob" files
 
  
 
When I go to the production system and run the "reportname.rpt" file from the 
R> prompt it crashes me out of Rbase and doesn't add the new/replaced report.
 
  
 
Thanks for any help you can provide.
 
  
 
Ron Peterson
 
--
For group guidelines, visit 
http://www.rbase.com/support/usersgroup_guidelines.php
--- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
[email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/rbase-l/DS0PR84MB341921A2BE4CC8BAFE6B8DD6C8F92%40DS0PR84MB3419.NAMPRD84.PROD.OUTLOOK.COM.
 
-- 
For group guidelines, visit 
http://www.rbase.com/support/usersgroup_guidelines.php
--- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
[email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/rbase-l/1909871544.522081.1739653723296%40mail.yahoo.com.
 

-- 
For group guidelines, visit 
http://www.rbase.com/support/usersgroup_guidelines.php
--- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/rbase-l/CY5PR11MB6259E362ADC53293FDD31CA7BAF92%40CY5PR11MB6259.namprd11.prod.outlook.com.
  

-- 
For group guidelines, visit 
http://www.rbase.com/support/usersgroup_guidelines.php
--- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/rbase-l/1545154880.1264374.1739889676727%40mail.yahoo.com.

Reply via email to