In article
<4da8b61e-cecc-4df7-9b4e-03c74cf2a269 (AT) q40g2000prg (DOT) googlegroups.com>,
"Tim D." <timothydavie (AT) gmail (DOT) com> wrote:
Quote:
On Aug 26, 1:20Â*pm, "Tim D." <timothyda... (AT) gmail (DOT) com> wrote:
If I understood David's message, his idea is to find the records I
want, then do a "Save A Copy As..." that includes those records. Then,
make an empty clone, and import the saved records from within the
clone. Is that right?
No idea why that posted 4 times. Sorry, not sure how to remove a post.
Weird. |
Several of your posts have gone through multiple times...
And no, you did not get what I said right!
"Save As" lets you save three different ways:
* a copy
* a compressed copy (smaller)
* a clone (an empty database with all fields, relationships,
scripts, etc. but no records)
In one of your other posts, you mention that size when transferring
from your computer to your iPhone is an issue. If you haven't done
this, try saving a compressed copy first, and see how big your
database ends up - that might possibly solve your problem right
there, and at least you'd have a backup copy of your database in
case things went wrong.
The Import and Export functions in the File menu are different
to saving, so you might want to read up in the documentation about
them. Basically, Export works on the current found set and allows
you to save those records in one of a variety of formats.
For what you want, what you could do is:
* Find the records you want to use within your desktop version
* Export those records, using e.g. FileMaker as a file format
* Copy that file to your iPhone
Alternatively, you could:
* Save as a compressed copy
* Open the compressed copy
* Find the records you don't want to use and delete them
* Copy the compressed copy with remaining records to the iPhone
The problem is if you modify or create any records on your iPhone
and want those changes back in the original - do you think you'd
want to do that, or simply use some subset of your database on the
iPhone?