Hello:

Wondering if anyone out there has had luck moving an Fp5 file with repeating
fields to a set of relational tables. I thought I was on to something based
on a reply to this newsgroup in a previous thread about cloning my fp5 file,
and then importing the records by specifying that repeating fields be split
into seperate records.

While that process seems to work fine, the tools that I use to then move it
to a relational system crashes in a big way. I'm on a wintel platform, and
have tried using DTS to move to MS SQL server, and then MS Access. Access
claims that there are too many indexes (and yes, I deleted all indexes in my
clones fp5, while the MS SQL tool crashes outright.)

Anyone??? Thanks.

"Paul Robinson \(mobile\)" <roro@telusplanet.net> wrote in message news:<IMWyb.91848$oN2.58413@edtnps84>...
> Hello:
> 
> Wondering if anyone out there has had luck moving an Fp5 file with repeating
> fields to a set of relational tables. I thought I was on to something based
> on a reply to this newsgroup in a previous thread about cloning my fp5 file,
> and then importing the records by specifying that repeating fields be split
> into seperate records.
> 
> While that process seems to work fine, the tools that I use to then move it
> to a relational system crashes in a big way. I'm on a wintel platform, and
> have tried using DTS to move to MS SQL server, and then MS Access. Access
> claims that there are too many indexes (and yes, I deleted all indexes in my
> clones fp5, while the MS SQL tool crashes outright.)
> 
> Anyone??? Thanks.

What happens if you clone the database, remove the repeating fields
(set to not repeat), import the repeating fields telling it to split
them.  Then export that to something that SQL Server or Access will
like, like a tab-delimited or CSV file.  Bit of a kludge, but then it
should work.  You could export to a series of text files and then in
Access import a file, then if it's successful, use something like
rename to move it.  Then the process is automatic... or nearly.