Razzak, What a wonderful clarification of the issue!
I'm going to have to try the UNLOAD ALL method again. All I'm missing is the variables I use embedded in some of the views, but I already have code to figure that out. This would certainly simplify things on the rare occasions we need to go this route. Being up-to-date would be even easier, I'm still dreaming about that!!! Dennis McGrath Software Developer QMI Security Solutions 1661 Glenlake Ave Itasca IL 60143 630-980-8461 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of A. Razzak Memon Sent: Friday, February 04, 2011 3:06 PM To: RBASE-L Mailing List Subject: [RBASE-L] - UNLOAD ALL vs UNLOAD DATA (was Re: Illegal table name) At 08:42 AM 2/4/2011, [email protected] wrote: >And I'm glad because my early experiences with unload weren't >good ones, with tables being created out of order (FK tables >before the PK tables), views out of order, etc... Don't know >if it's a cleaner experience now, I'm sure it is. My last >unload was probably a few years ago. It's funny you mentioned this! If you use "UNLOAD ALL" and then RUN the file to re-build the database, you will NOT see such issue. R:BASE engine takes care of the table sequence and dependency. If you UNLOAD STRUCTURE as a separate file, and then UNLOAD DATA as a separate file, and then RUN the file with STRUCTURE, and then RUN the file with DATA, you might see such behavior. This is a legacy boo boo we all have lived with. However, this MAJOR engine-level fix has been implemented in the latest available versions of R:BASE eXtreme 9.1 (32/64), to be officially released on February 14, 2011. This is a result of a major 9.1 (64) conversion project that I have been involved with. http://www.rbase.com/rbg91/ Very Best R:egards, Razzak.
