Jim,

 

Sorry I wasn't more specific.  Yes, you need to either rename or move the
main database before you start building the new one.

 

Emmitt Dove

Manager, Converting Applications Development

Evergreen Packaging, Inc.

[email protected]

(203) 214-5683 m

(203) 643-8022 o

(203) 643-8086 f

[email protected]

 

From: [email protected] [mailto:[email protected]] On Behalf Of Jim Belisle
Sent: Tuesday, June 16, 2009 6:29 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - RE: MAINTENANCE

 

Emmett,

 

This type of maintenance is all new to me so please forgive the simple
questions.  Am I supposed to either give the UNLOAD DB a new name or put it
on a different dir?  I did what you mentioned below using the same DB name
and it gave me an error.  (Duplicate Tables & DB)

 

Jim

 

 

  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of Emmitt Dove
Sent: Tuesday, June 16, 2009 7:38 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - RE: MAINTENANCE

 

Jim,

 

I would do  this:

 

OUTPUT dbname.str

UNLOAD STRUCTURE

OUTPUT SCREEN

 

OUTPUT dbname.dat

UNLOAD DATA

OUTPUT SCREEN

 

Now you have your data and structure in two different files.  Edit
dbname.str and find the section where it creates the autonumbers.  Cut that
section and write it to a separate file, say makenums.cmd. 

 

Now:

 

RUN dbname.str

RUN dbname.dat

TRACE makenums.cmd

 

While tracing the makenums.cmd you should find the error.

 

Emmitt Dove

Manager, Converting Applications Development

Evergreen Packaging, Inc.

[email protected]

(203) 214-5683 m

(203) 643-8022 o

(203) 643-8086 f

[email protected]

 

From: [email protected] [mailto:[email protected]] On Behalf Of Jim Belisle
Sent: Tuesday, June 16, 2009 7:13 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - MAINTENANCE

 

I am attempting to make sure I have a 'CLEAN' database by following RAZZAK's
10 step instructions.  I followed the instructions up to the RUN newdb.ALL.
Things were running smoothly until I got an ERROR 687 Autonum columns must
be Integer etc.  I had no idea what table it was referring to since that did
not show up on the screen.  I started over using the TRACE newdb.ALL
command.  When it got to the same place it just gave me another command and
stopped.  It did not give me a chance to change anything.  The cursor just
went to the R prompt.

 

What can I do next to FIND the problem?

 

Jim

 

 

Reply via email to