dbTalk Databases Forums  

"Saving" data

comp.databases.filemaker comp.databases.filemaker


Discuss "Saving" data in the comp.databases.filemaker forum.



Reply
 
Thread Tools Display Modes
  #11  
Old   
Your Name
 
Posts: n/a

Default Re: "Saving" data - 03-24-2010 , 07:26 PM






In article <1jfwk49.1uyfrjq1zcfc8N%dempson (AT) actrix (DOT) gen.nz>,
dempson (AT) actrix (DOT) gen.nz (David Empson) wrote:

Quote:
Your Name <your.name (AT) isp (DOT) com> wrote:

"David Empson" <dempson (AT) actrix (DOT) gen.nz> wrote in message
news:1jfvi3m.retmgm1cp96x6N%dempson (AT) actrix (DOT) gen.nz...
Your Name <your.name (AT) isp (DOT) com> wrote:

Unless it's something added to the newer versions (and I haven't
looked in FileMaker 9), you can't "export" records as a FileMaker
file.

FileMaker Pro 7 and later can export as a FileMaker Pro database. It
produces a simple database with a single table containing the data from
the exported table.

Seems a bit of a silly addition (especially since you'd lose any the related
data) considering what else is still "missing". No doubt some people find it
useful, but it really just removes one step from an "Export to Excel, Import
to FileMaker" process ... although it would keep the Container Field data.

For that matter, so can FileMaker Pro 6. (Isn't that the version you are
running?)

Nope. I've got FileMaker 4 and 5.5.

Well you didn't look very hard. FileMaker Pro 5.5 has the same feature.

(I can't run FileMaker Pro 4 any more without digging out an older
computer.)
You're right. It does have that option ... weird that I've never noticed
it before, but then I can't see any real point for it, especially in the
older versions where there was only one table per file anyway. It only
saves a few extra seconds work deleting unwanted records.

Helpful Harry )

Reply With Quote
  #12  
Old   
David Empson
 
Posts: n/a

Default Re: "Saving" data - 03-25-2010 , 12:56 AM






Your Name <your.name (AT) isp (DOT) com> wrote:

Quote:
In article <1jfwk49.1uyfrjq1zcfc8N%dempson (AT) actrix (DOT) gen.nz>,
dempson (AT) actrix (DOT) gen.nz (David Empson) wrote:

Your Name <your.name (AT) isp (DOT) com> wrote:

"David Empson" <dempson (AT) actrix (DOT) gen.nz> wrote in message
news:1jfvi3m.retmgm1cp96x6N%dempson (AT) actrix (DOT) gen.nz...
Your Name <your.name (AT) isp (DOT) com> wrote:

Unless it's something added to the newer versions (and I haven't
looked in FileMaker 9), you can't "export" records as a FileMaker
file.

FileMaker Pro 7 and later can export as a FileMaker Pro database. It
produces a simple database with a single table containing the data from
the exported table.

Seems a bit of a silly addition (especially since you'd lose any the
related data) considering what else is still "missing". No doubt some
people find it useful, but it really just removes one step from an
"Export to Excel, Import to FileMaker" process ... although it would
keep the Container Field data.

For that matter, so can FileMaker Pro 6. (Isn't that the version you are
running?)

Nope. I've got FileMaker 4 and 5.5.

Well you didn't look very hard. FileMaker Pro 5.5 has the same feature.

(I can't run FileMaker Pro 4 any more without digging out an older
computer.)

You're right. It does have that option ... weird that I've never noticed
it before, but then I can't see any real point for it, especially in the
older versions where there was only one table per file anyway. It only
saves a few extra seconds work deleting unwanted records.
And fields. You can export only the data (records and fields) you want,
and send it to someone without having to give them a complete copy of
your database.

I can see potential uses if there are security concerns over giving
somewhat else access to all of the data.

--
David Empson
dempson (AT) actrix (DOT) gen.nz

Reply With Quote
  #13  
Old   
Howard Schlossberg
 
Posts: n/a

Default Re: "Saving" data - 03-25-2010 , 11:09 AM



Quote:
Your Name <your.name (AT) isp (DOT) com> wrote:

You're right. It does have that option ... weird that I've never noticed
it before, but then I can't see any real point for it, especially in the
older versions where there was only one table per file anyway. It only
saves a few extra seconds work deleting unwanted records.

And fields. You can export only the data (records and fields) you want,
and send it to someone without having to give them a complete copy of
your database.

I can see potential uses if there are security concerns over giving
somewhat else access to all of the data.

I use this option often when I need to export data with field names so
that I can later import the data using 'matching field names'. It is
more reliable for this then either DBF or MER exports.

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.