Exporting All Fields fails? 
Author Message
 Exporting All Fields fails?

I'm using FMP3 and I've struck an odd problem with "Export".

I clear all fields using the button, then move all fields, however, one
field is not moved over. It happens to be a calculation field that
calculates a container but that shouldn't matter. It should be in the list
and it should produce  an empty field for export. My backups do the same
thing - curses.

Why would FMPro refuse to export a field? Has anyone else seen this before?

--
Malcolm Fitzgerald
Database Manager
The Australian Society of Authors


http://www.***.com/



Sun, 24 Aug 2003 13:56:48 GMT
 Exporting All Fields fails?

Hi Malcolm

What format you are exporting in?  I can't get the container fields or
container calc field to move over to the right if I am exporting  as
tab-separated text either (using v4 on a Mac), but I assume that is
normal, since you obviously can't export a graphic as text - well, not in
a meaningful or useful way, at any rate.  If you select FileMaker Pro
format, they move across and export as you would expect them to.

--
Bridget Eley


Quote:

> I'm using FMP3 and I've struck an odd problem with "Export".

> I clear all fields using the button, then move all fields, however, one
> field is not moved over. It happens to be a calculation field that
> calculates a container but that shouldn't matter. It should be in the list
> and it should produce  an empty field for export. My backups do the same
> thing - curses.

> Why would FMPro refuse to export a field? Has anyone else seen this before?

> --
> Malcolm Fitzgerald
> Database Manager
> The Australian Society of Authors


> http://www.asauthors.org



Sun, 24 Aug 2003 15:04:21 GMT
 Exporting All Fields fails?
I'm exporting Comma separated values and I've been used to getting empty
values in the places where there are container fields. Maybe my question
should be "Why does FM display container fields in the Right Hand column -
FM shouldn't export container fields".

The oddity is that the file contains a lot of container fields and
calculations that end up being containers. When I "clear all" and "move all"
I see all of the fields ( except the one I mentioned ) appear in the right
hand column. That leads me to think that I'm going to get a value (albeit
empty) in the output. The results I get may be consistent with FMPro NOT
exporting containers because the data sets do not correspond with the
headers that I've generated from screen shots of the Right column.

Quote:
> Hi Malcolm

> What format you are exporting in?  I can't get the container fields or
> container calc field to move over to the right if I am exporting  as
> tab-separated text either (using v4 on a Mac), but I assume that is
> normal, since you obviously can't export a graphic as text - well, not in
> a meaningful or useful way, at any rate.  If you select FileMaker Pro
> format, they move across and export as you would expect them to.

> --
> Bridget Eley



>> I'm using FMP3 and I've struck an odd problem with "Export".

>> I clear all fields using the button, then move all fields, however, one
>> field is not moved over. It happens to be a calculation field that
>> calculates a container but that shouldn't matter. It should be in the list
>> and it should produce  an empty field for export. My backups do the same
>> thing - curses.

>> Why would FMPro refuse to export a field? Has anyone else seen this before?



Mon, 25 Aug 2003 08:37:16 GMT
 Exporting All Fields fails?
It can export container fields, providing the selected format is able to
receive them, such as when you export to FileMaker Pro format. Exporting
to FileMaker Pro format is quite interesting: I once thought you might be
able to use it as an rough and ready archival feature (since none of the
layouts, scripts, relationships or value lists are reproduced) but you
can't because of the way it handles calculation fields.  Calc fields are
converted to the type of field that their result would be if not a
calculation.  This means that calculations that produce container results
are transformed into container fields with the resulting graphic object in
them.  A database that heavily uses graphics in a container field via the
Get Repetition function will end up being twice as large because each
graphic object is now a separate object!  However, it does raise an
interesting possibility for a rough and ready way of replicating fields
(except calc fields) from an existing solution.  Fields are replicated in
custom order too which is neat.

--
Bridget Eley


Quote:

> I'm exporting Comma separated values and I've been used to getting empty
> values in the places where there are container fields. Maybe my question
> should be "Why does FM display container fields in the Right Hand column -
> FM shouldn't export container fields".

> The oddity is that the file contains a lot of container fields and
> calculations that end up being containers. When I "clear all" and "move all"
> I see all of the fields ( except the one I mentioned ) appear in the right
> hand column. That leads me to think that I'm going to get a value (albeit
> empty) in the output. The results I get may be consistent with FMPro NOT
> exporting containers because the data sets do not correspond with the
> headers that I've generated from screen shots of the Right column.

> > Hi Malcolm

> > What format you are exporting in?  I can't get the container fields or
> > container calc field to move over to the right if I am exporting  as
> > tab-separated text either (using v4 on a Mac), but I assume that is
> > normal, since you obviously can't export a graphic as text - well, not in
> > a meaningful or useful way, at any rate.  If you select FileMaker Pro
> > format, they move across and export as you would expect them to.

> > --
> > Bridget Eley



> >> I'm using FMP3 and I've struck an odd problem with "Export".

> >> I clear all fields using the button, then move all fields, however, one
> >> field is not moved over. It happens to be a calculation field that
> >> calculates a container but that shouldn't matter. It should be in the list
> >> and it should produce  an empty field for export. My backups do the same
> >> thing - curses.

> >> Why would FMPro refuse to export a field? Has anyone else seen this before?



Mon, 25 Aug 2003 11:18:16 GMT
 Exporting All Fields fails?

Quote:
> It can export container fields, providing the selected format is able to
> receive them, such as when you export to FileMaker Pro format.

yes, just what causes the problem I don't know but I've had a different set
of results every time I've done the export. I am attempting to export CSV.
FMP displays a set of fields in the right hand column, ie, fields to export,
however it doesn't export them all. Why does it list them? It has been
causing me a lot of trouble. The database has 167 fields and it is easy to
make a mistake, to miss one or get the wrong one. I thought that the best
way to ensure I got it right was to take the lot and modify the results in a
spreadsheet. When that failed I realised that I wasn't getting all the
fields so I took screen shots of all the field names that were in the right
hand column, grabbed the list of field names from the file via AppleScript,
then used them to build the same list as I had got from the screen shots. At
this point I'd expect that I had it right but there are still differences
between the list of field names and the actual output. grrr

Quote:
> Exporting
> to FileMaker Pro format is quite interesting: I once thought you might be
> able to use it as an rough and ready archival feature (since none of the
> layouts, scripts, relationships or value lists are reproduced) but you
> can't because of the way it handles calculation fields.  Calc fields are
> converted to the type of field that their result would be if not a
> calculation.  This means that calculations that produce container results
> are transformed into container fields with the resulting graphic object in
> them.  A database that heavily uses graphics in a container field via the
> Get Repetition function will end up being twice as large because each
> graphic object is now a separate object!

You want to "Save a Copy", the export is essentially a snapshot of the
current state of the document, ie, 14 of 300 records formatted according to
current layout. However, you can save a clone of the database, then use the
clone to import the current found set.
Quote:
> However, it does raise an
> interesting possibility for a rough and ready way of replicating fields
> (except calc fields) from an existing solution.  Fields are replicated in
> custom order too which is neat.

> --
> Bridget Eley



>> I'm exporting Comma separated values and I've been used to getting empty
>> values in the places where there are container fields. Maybe my question
>> should be "Why does FM display container fields in the Right Hand column -
>> FM shouldn't export container fields".

>> The oddity is that the file contains a lot of container fields and
>> calculations that end up being containers. When I "clear all" and "move all"
>> I see all of the fields ( except the one I mentioned ) appear in the right
>> hand column. That leads me to think that I'm going to get a value (albeit
>> empty) in the output. The results I get may be consistent with FMPro NOT
>> exporting containers because the data sets do not correspond with the
>> headers that I've generated from screen shots of the Right column.

>>> Hi Malcolm

>>> What format you are exporting in?  I can't get the container fields or
>>> container calc field to move over to the right if I am exporting  as
>>> tab-separated text either (using v4 on a Mac), but I assume that is
>>> normal, since you obviously can't export a graphic as text - well, not in
>>> a meaningful or useful way, at any rate.  If you select FileMaker Pro
>>> format, they move across and export as you would expect them to.

>>> --
>>> Bridget Eley



>>>> I'm using FMP3 and I've struck an odd problem with "Export".

>>>> I clear all fields using the button, then move all fields, however, one
>>>> field is not moved over. It happens to be a calculation field that
>>>> calculates a container but that shouldn't matter. It should be in the list
>>>> and it should produce  an empty field for export. My backups do the same
>>>> thing - curses.

>>>> Why would FMPro refuse to export a field? Has anyone else seen this before?



Tue, 26 Aug 2003 09:34:44 GMT
 
 [ 5 post ] 

 Relevant Pages 

1. Exporting fields with array fields (and a date format question)

2. Add field with Boolean field type failed using ADOX

3. DTS Export: How to have nulls export as blanks on fixed width export

4. Exporting a table from microsoft access to ms sql 6.5 fails

5. Exporting data to Local DB Fails

6. DTS to export database fails

7. DTS Export Wizard fails on queries

8. Error upsizing Access2000 database to SQL6.5 ('Table was skipped, or export failed)

9. DTS Export to Oracle fails with nulls

10. DTS Export with binary data fails

11. SQL Server Upgrade Wizard Fails During Import/Export

12. Export Data fails


 
Powered by phpBB® Forum Software