Hi, He could always use the other method of copying the report.
Database1 is the source and Database2 is the destination. Set up Database2 as a odbc connection if it isn't already. Start Rbase, open Database1 SCONNECT Database2 SATTACH sys_reports3 AS otherreport INSERT INTO sys_reports3 SELECT * FROM otherreport WHERE sys_report_name='reportname' SDETACH otherreport SDISCONNECT Database2 Ted -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Emmitt Dove Sent: Monday, August 09, 2004 8:07 AM To: RBG7-L Mailing List Subject: [RBG7-L] - RE: Copy Report To Another Database Any UNLOAD DATA FOR tablename will do this for you, using the NULL setting for the database. We always set NULL to the dash (CHAR(45)), and have since 3.x without any problems. >I'll wait for a comment from Dr:R: but I certainly feel much safer when >my db has NULL -0- before moving any data at all in any direction. >Suspenders and belt? Probably <g> > >--- Lawrence Lustig <[EMAIL PROTECTED]> wrote: > > > > One minor amendment: SET NULL -0- before unloading the report > > > data. > > > > Is this still true in "modern" R:Base? I don't think any of the > > form and report tables' columns are every null. . . Except maybe for > > the comment, which doesn't really matter if it gets set to a 0 > > length string. > > -- > > Larry > > > > > > >===== >Albert Berry >Management Consultant >RR2 - 1252 Ponderosa Drive >Sparwood BC, V0B 2G2 >Canada >(250) 425-5806 >(250) 425-7259 >(708) 575-3952 (fax) >[EMAIL PROTECTED] Emmitt Dove Manager, DairyPak Business Systems Blue Ridge Paper Products, Inc. 40 Lindeman Drive Trumbull, CT 06611 (203) 673-2231 [EMAIL PROTECTED] [EMAIL PROTECTED]
