Jump to content

Field Format Problem After Export


This topic is 7087 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies

I am working on exporting data out of a custom-created FileMaker 5.5 database to import into eBase. One of the fields is a series of check boxes for a value list called "Groups." When I export data into .CSV, all of the data from that field is placed into a single field, separated by "boxes." I originally assumed that these "boxes" were line breaks. But, I do not believe that they are now. My problem is that I cannot do much of anything with the data while it is all concentrated into one field. And, since I cannot figure out what the data separator character is, I'm really quite stuck. I've attached a sample of the data. If anyone can provide assistance, I would greatly appreciate it. Thanks.

Sample.zip

Link to comment
Share on other sites

The box is a "vertical tab", ASCII 11, which FileMaker must use in order to not screw up the .csv, because 1 record = 1 line; can't handle extra line endings.

One way to do it is to create a FileMaker calculation, using Substitute() to convert those to a comma, then export the calculation field instead. The quotes in the CSV should allow you to have commas in a text field.

But one wonders why, since eBase is FileMaker, you don't just import as FileMaker? Other than the fact that eBase is kind of convoluted. Of course, much of that is to flexibly handle security/viewing with user-configurable fields. I haven't looked at their 7 version; hopefully it's been streamlined.

Link to comment
Share on other sites

This topic is 7087 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.