Hi all, I've been posting about problems using EOUtil and ModelerBundle. I was pointed at using EOUtil but misunderstood that EOUtil is a command line app. I did a search, found ModelerBundle in the examples directory, installed it, and tried to use the Export and Import functions from within EOModeler. Garrick McFarlane was good enough to write me and tell me that EOUtil can be run from the command line (so that's what NSTask is being use for :\ ). He told me to run the command from EOModeler and look in the console for the command syntax (Application Event Log in NT). I did, and ran the command from a command prompt and it worked great. Plus, I can now script it. Take my old model file and the new one, export all tables, then import into the other. All while I'm at lunch today :). Here is the output of the export command for my Contacts table. C:\Apple/Developer/Examples/EnterpriseObjects/SetupWizard.app/Resources/eout il.exe dump C:\ExportedRows\HO\HO_1.eomodeld -task -entities Contacts -source database -dest plist C:\ExportedRows\Contacts.plist -modelGroup C:\ExportedRows\HO\HO_1.eomodeld and here's the import command C:\Apple/Developer/Examples/EnterpriseObjects/SetupWizard.app/Resources/eout il.exe dump C:\ExportedRows\HO2\HO_1ob.eomodeld -task -entities Contacts -source plist C:\ExportedRows\Contacts.plist -dest database -modelGroup C:\ExportedRows\HO2\HO_1ob.eomodeld Notice that the only difference is the -source and -dest flags. BTW, you do *keep* the forward slashes in the first line. The above is exactly what I have in a .BAT file. Also, the export and import really draged down my NT 4 Server with 96 MB RAM. Garrick suggested closing the console window. NT is going to write to the command prompt window though so I don't know a way around that. Thanks for the help everyone. EOUtil really completes EOModeler. I can easily export all my data from my Paradox database and import it into (in this case) OpenBase or whatever database I want. Very nice. --Marc Respass
