capture import errors

#1

Hello again--

Another question that has been nagging me and wondering if anyone has
a workaround:

When importing a table, of say 5,000 records and 4,000 import fine but
1,000 do not (arbitrary numbers) Is there a way to capture WHICH 1,000
records did not import correctly?

Yes, I suppose I could create a blank database with no field
constraints, import the 5K into that and relate it to the database
that only accepted 4K to see the records not present, but I was
looking for a more direct solution...

any thoughts?

thanks-
sg

#2

In article
<1181223878.519135.251190 (AT) g4g2000hsf (DOT) googlegroups.com>MaximalVariance
<StephenTGallagher (AT) gmail (DOT) com> wrote:

Quote:

Hello again--

Another question that has been nagging me and wondering if anyone
hasa workaround:

When importing a table, of say 5,000 records and 4,000 import fine
but 1,000 do not (arbitrary numbers) Is there a way to capture WHICH
1,000records did not import correctly?

Yes, I suppose I could create a blank database with no field
constraints, import the 5K into that and relate it to the database
that only accepted 4K to see the records not present, but I
waslooking for a more direct solution...

any thoughts?

What do you mean by not importing correctly? Is it a data type
mismatch? If so, would the isValid function be of help?
Matt

--
I'm trying a new usenet client for Mac, Nemo OS X.
You can download it at http://www.malcom-mac.com/nemo

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

capture import errors

comp.databases.filemaker comp.databases.filemaker

capture import errors - 06-07-2007 , 08:44 AM

Re: capture import errors - 06-08-2007 , 04:18 PM