Hi, Mark - Thanks for your help - on a Sunday, no less! My answers are in
line below.
----- Original Message -----
From: Mark Nepon
To: Dataperfect Users Discussion Group
Sent: Sunday, August 19, 2007 11:10 AM
Subject: Re: [Dataperf] I need help with a dumb question!
Hi Laurie,
Check over the indexes to this carefully.
Are you using log files to import or Ctrl-F5? When importing are you allowing
new number in auto-inc or using number from datafile?
---I am using Ctrl-F5. The files I am importing are Wordperfect 5.1 merge
files, not log files. The import is set to renumber the records as they are
imported. (The records in the imported files themselves do not contain any
numbering at all. They consist of simply a series of text fields.)
If fields were added then the info being exported from 1 database to another
(I assume temp database is another) then their may be a problem in the order of
the fields as they're being imported.
-- The fields that were added a few months ago were in another panel, not the
panel I am importing into, so I really don't think this is affecting the
import. The files I am importing aren't from another database. They are just
WordPerfect merge files that were actually created in WordPerfect, and they
have not changed in field order, either. The panel they are importing into is
just used as a temporary import panel -- data is imported into it and then a
report is run on the data which puts the data into the correct panels in the
rest of the database and then deletes the records from the temporary inport
panel. The problem is occuring at the time of import, before the report has
even been run. The import panel itself just consists of 1) the
autoincrementing field, and 2) a bunch of variable length text fields, which of
course don't care what kind of data gets imported into them, so field order,
even if it had changed, shouldn't really be an issue. The autoincrementing
field, of course, is not getting anything imported into it. All the incoming
WP merge fields are going into the variable length text fields.
You should assess the info in the file used for import to be sure it has all
the info for all the fields.
-- I checked the files being imported - they are complete and this does not
appear to be the problem. Also, if I split up the files into smaller files,
they will import. This would argue against the data itself being the problem.
It is only the SIZE of the imported file which seems to be causing the
problem. However, for years previous to Friday, much larger files have
imported without problems.
You might try importing this data to an empty database of the program and see
if they all import.
-- This is a good idea. I will try this now as soon as I can get an empty
database set up to try this on. However, if this works, what does this tell me?
When you did the big clean did you ensure the database was working properly
prior to importing the data. Sometimes the indexes or fields go "kaflooey."
During the import of the database structure the aspect of what was causing the
problem that required the big clean is not fixed during the import of the
database structure but ignored. So you may have lost some of the database
structure. Presumably a very small thing like a missing index or a changed
index.
-- I didn't even think of this. Whatever the problem was, however, I believe
it existed before I did the Big Clean. (That's why I did the Big Clean - with
the hope that it would fix whatever the problem was. --The problem I am having
is the same one I was having before the Big Clean.)
You may have to re-define some links particularly that were based on this
messed up index.
These are some of the things to look for.
Hope it helps. I had about 5 minutes to think about this.
If need be perhaps you can send me a copy of the database and if I have time
I may be able to help you with it. Can't promise anything.
-- I would hate to subject you to my mess, so hopefully an answer will be
found some other way! My *.STR file size is listed at 3,425,792. I am
wondering if I have hit some sort of size limit for either the STR file, or the
index or TXX files. Does anyone know what the size limit is? (practical, not
theoretical)
--Thanks again for your help! Laurie
all the best,
mark nepon
----- Original Message -----
From: Laurie Corvacho
To: Dataperfect Users Discussion Group
Sent: Sunday, August 19, 2007 10:27 AM
Subject: [Dataperf] I need help with a dumb question!
Hello, everyone!
It's been a long time and I'm embarrassed to write to the list after so
many years incommunicado with everyone (except for Brian a while back).
I have a dumb question and I can't find it in any of my reference books.
I did the "Big Clean" but my reports aren't displaying while they are
printing - you just see a number counting as it goes through the records. I
know this is a very simple setting but I can't remember how to get to it, and I
can't find how to reset it in my manuals or Ralph's book. (Probably panic is
interferring with effective searching!) Can someone tell me how to set it back
so the reports display while they are printing.
I am also having another (bigger) problem. I have my DP application that I
have been using and tinkering with for my home-based business for 10+ years and
it has been working fine all this time. However, on Friday morning I started
having a problem with importing records into it into my temporary import panel.
When I try to import a file, the records at the beginning of the import
file import correctly, but the rest of the records are blank. The number of
records that is created in the import panel corresponds to the number of
records in the import file, but after a certain point in the import file, the
only field that is populated is the autoincrementing number field. All the
other fields are blank. The last record that imports any values at all into
the fields only imports some of the fields. If I divide up the file into small
enough files and import each one separately, they each import correctly -- kind
of (I'll explain that if needed.)
The number of records that imports correctly has been getting progressively
smaller over the past 2-3 days. Initially it was, say, 800 out of 1200, then
it went down to 400 out of 1200, and now it is down to about 175 and presumably
getting smaller.
I have tried the import on various computers, and the exact same thing
happens on all of them, so the problem is not confined to a single workstation
Does anyone know what could cause this? As mentioned above, I have done
the "big clean" in an attempt to try to fix whatever must have gotten messed
up. No other changes were made to the database prior to this problem
occurring, except for about 2-3 months ago when some new fields were added to a
panel and some new reports were added to the reports list. Again, that was
some months ago, and there had been no problems up until this problem just
started occurring on Friday.
Please help!
Laurie Corvacho
----------------------------------------------------------------------------
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
------------------------------------------------------------------------------
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
