Odd Problem

[SteveB]

Using Dev 5.5 on XP platform to develop a runtime. The odd problem has to do with importing data to upgrade a solution. The problem only happens with 1 file out of a total of 20. The old files are stored in an Old folder. I do an import from the old file into the new using a script with four lines:

All User Abort(OFF)

PerformScript(External: Show all records in old file)

Import(Restore Order, No Dialog, Old File)

SetField(Found Count, Status(CurrentFoundCount)

If I run the script manually, the import works fine. After making a runtime, the same script doesn't import any data. I know the script is being executed because I log the upgrade steps procedure. Something about the Import and the conversion to a runtime (with a new file extension) seems to be screwing up. I've already recovered the file, but it didn't help.

Steve

[rogermax]

Steve, Does the source file have a different file extension after binding than when you manually do the import? Does seem odd that it is only one of 20 files.

I tend to start the upgrade from the Old files by running a script that makes a copy with a different name then code that name in the new solution for upgrade. Kind of a prep step then it closes and the new is opened and starts the import fromthe renamed files.

[SteveB]

Roger: Yes, the files have a different extension, which I beleive is the real problem. I've had similar problems like this in the past. I'm going to rename the file in Developer and see if that solves this problem.

Steve

[Oldfogey]

Have you opened your runtime file with FMD and checked the filename in your script?

I use your technique for upgrades and FMD actually had the sense to rename my original filenames! I still do it myself, though, because I don't trust software developers.

[SteveB]

I can't open the runtime in FM because I use Dacons Menu Control, and the runtime gets screwed up if you try and restore the original FM Menus. I've tried renaming the offending file, recovering the file, exporting the data out of the file into a temp FP5 file and then importing into the new file all with no luck.

Steve

[Oldfogey]

Have you checked your underwear?

OK, so copy the offending file and open the copy with FMP. At least you'll know if it's got the correct filenames.

Any chance your file is corrupt? How big a job is it to re-build it?

[DykstrL]

Steve,

The binding key is what determines whether a file can be opened with a runtime engine. If the keys are different and the extension is the same, the file cannot be accessed.

another method is - in the old version - create an export script to show all records and export the records to a FileMaker (.FP5) file. Then in the new version create a script to import the .FP5 file, then you can use Applescript or a BATch file to delete the old files. As long as the binding key is the same, it will work.

[SteveB]

dykstrl:

You're missing the point. My imports work in all but one file. Please re-read my original post, as it has nothing to do with the binding key.

Steve

[Oldfogey]

Have you opened the Old file to make sure your Show_All_Records script is working?

Sorry, if i'm being simple but I've been caught.

I think I'd be talking to FMI.

[SteveB]

Yes, that's the first thing I do. I think my only choice is to re-build the file.

Steve