We have an old database that we need to export all of the content including containers. Is there a way to do this?
As long as insert object was not used, you should be able to use export field contents. A script could loop through your records and use this step to export.
With the file being so old I am not sure how the documents were added to the containers. Does anyone have a script that could be used?
It really isn’t clear what your question is.
Why not just export all of the content including containers?
Are you able to open the file?
Export: in what format? CSV? Tab delimited?
How many tables are in the file?
What do you hope to do with the results?
How big is the file?
Do you just want to see your old data?
Maybe show all records and print as PDF.
In version 7 there is not an option to export the containers.
Yes, I am able to open the existing file.
We can export to cvs but it does not include the contain files.
We are trying to migrate the data but need to include all data including documents in the containers.
The file is 32.2 GB, 12,127 records.
Our goal is to migrate the data.
migrate to a newer FileMaker or to another ('foreign') system?
- a newer FileMaker version can read V7 data, opening in V16 will convert the file(s) to .fmp12
- a foreign system might need the data and the container-data (separate) with the ID (to the FM records)
Better check again. The export field contents script step, according to FileMaker help, was introduced in FileMaker 6.
Ya. As Markus told above, Convert your fp7 to fmp12 by opening the old file in New FileMaker UI. Then Export your all data including containers without any issue!
It looks he want to migrate to foreign system. There is no need to "export" to migrate to newer FM, converted file can be used to "import" on new system. Exporting records can't contain container field other than FM format. It makes only simplest layout without any script in the file than converted file.
If there is no "Export field contents", it is OLE object as mentioned in first reply. You need saving them one by one.
e.g. if the document is Excel workbook, (you need installed Excel in the PC?) double click the container to open embeded document (with host app ?), save it (in host app's menu ?).
I am running into a similar issue as well. I am trying to upgrade from FM11 (.fp7) to FM16 (.fm12). We have a 12 yr old application that we are trying to upgrade (originally created in FMP8. We have nearly 46,000 attached documents in the container fields. These are mostly .doc and .pdf files. When I convert the file using FMP16, it appears to convert the container. I can see there is a file in the container, but I cannot export or open the file.
Is there any option besides opening the files from within .fm7 file, and manually attach it in the new one DB, which by estimates will be weeks worth of mind numbing work for someone (if they don't quit first) and has a lot of room for errors.
So, it certainly is not without issue.
Sounds like files inserted as objects. If so, then my sympathies as there is no easy solution for you that I know of. (I suspect that this particular issue was part of why Filemaker stopped supporting OLE.)
But if you see text such as "file not found" in the container field, it's possible that "store a reference" was used and then you might still be able to fix this.
NWbutcher wrote: Is there any option besides opening the files from within .fm7 file, and manually attach it in the new one DB, which by estimates will be weeks worth of mind numbing work for someone (if they don't quit first) and has a lot of room for errors.
Not sure what you mean with "manually attach it in the new db", but if the old containers used OLE: then no. There is no automated way to get that out, it has to be done manually.
Getting them into the new db however does not need to be done manually necessarily, If you are careful about how you name the exported files you could create a script in the new db that imports those in a loop.
Regardless of the method used to insert the files into the new db, it will be a tiny fraction of the time required to get the files out of the old db. My concern is "will FM make it so we have to go to similar extreme efforts in the future when a new upgrade comes out that will not once again convert attached files?"
NWbutcher wrote: My concern is "will FM make it so we have to go to similar extreme efforts in the future when a new upgrade comes out that will not once again convert attached files?"
My concern is "will FM make it so we have to go to similar extreme efforts in the future when a new upgrade comes out that will not once again convert attached files?"
Impossible to say. FMI goes to great lengths to preserve backwards compatibility. The Send DDE script step is a great example of that for instance. So is the fact that we haven't had a file format change in coming up 6 versions now.
But once in a while a technology jump needs to be made. OLE embedding is a victim of such a jump. Microsoft itself is moving away from the old OLE and ActiveX controls so supporting it going forward was going to be difficult I'm sure.
I certainly understand the technology will always, and needs to continue to march forward, but I don't think FM has ever supported as way to convert FileMaker solutions that had used OLE into current FileMaker solutions (Post OLE).
Retrieving data ...