I have been struggling with the upgrading process for the runtime and read up all the past thread with regards to this but I still could not figure it out.

I have created a runtime solution but before I roll it out, I want it to be prepared for the next upgrade. I am trying to call a function in the previous solution file to export out all the records from my new solution file, so that I can import it into new solution file. But I could not get it to excute accross the solution.

Can anyone show me what is the proper way to do an export and importing of the data into the new solution? Thanks.

Rdgs,

Stacey

I'm assuming that the previous version was 6 or earlier. V7 to v8 shouldn't be a problem, since the file format is pretty much the same. I don't believe that you can import data from fp5 files directly to fp7 files. My suggestion would be to create a .mer file for export from the old solution, and then import these files into the new version.

I know its hard to believe that FMI didn't provide a direct export/import.

Steve

Actually, no ...it is from v8 to v8 (runtime version) I am trying to include a upgrade feature for my program so that I can send off upgrade to them and with a click of a button, it will moved the data from the old database to the new database. But I cannot think of a better way then then to get the user to:

1. Go to the old file, click on a button, that will export out all the data from the current file.

2. Go to the new file, click on a button to import in the old data into the new file.

I want to automate the process but was unable to do it. I tried to call a script in the old runtime file from my new runtime file but apparently it fail to run.

Any anyone can help? Thanks.

You should be able to automate the procedure. And you should be able to run a script in the old file that is triggered from a script in the new file. Are your file references hardcoded? Are they correct?

Steve

Oh gosh ... yes ... I changed the path from relative path to hardcoded path ... and it works! There must be some problem with my file reference, though I still think that relative path should work. Well, at least I have a solution now, figure out the rest later. Took me so long to get that right. Thanks a millon for that pointer, Steve!