I have created a solution that seems to work fine until it calls for a particular database. A message pops up and says that "tickets.fp7" could not be opened. (Not Found) If I click the OK the open file opens and I can navigate to the tickets database in my solution folder. Selecting the file and then opening it makes my solution work. Any ideas on why I might be getting this message and a possible solutuion to my problem?

Thanks

DJMiller:

Perhaps you moved "tickets.fp7" from it's original location relative to the file that's calling it? Go to whatever script (or relationship) is calling tickets.fp7, and see where it's pointing. Chances are, it's wherever tickets.fp7 used to be. Point it to the existing file, and you should be fine.

If you've got loads of scripts/relationships pointing at the old location, it may be easier to move tickets.fp7 back to where it used to be.

-Stanley

I had thought the same thing, but none of the files have ever been moved. Everything is where it should be. And everything points to the correct location.

If it runs prior to creating a solution and finds the correct files, shouldn't it find the correct files once I actually create the solution?

Ah, wait, you're creating a runtime! Is the tickets.fp7 file a part of the runtime, or kept separate?

-Stanley

There are 17 databases in this solution. Tickets is one of them. When I create the run time, developer does its thing. The tickets database as well as the rest of the databases shows up in the newly created folder. I just can't figure out why when I start the run time application it will not find the tickets database without me manually telling it where it is.

DJ:

All the other files in the runtime are found without a problem? If so, there are two possibilities:

1) Your tickets.fp7 (or the db calling it) is corrupt and will have to be rebuilt.

2) The error pre-exists (which I imagine you've checked for) in the db calling tickets.fp7 (i.e., broken relationship or whatever.)

-Stanley

If I didn't already shave my head I'd still be bald for pulling my hair out. I did a recover on the tickets.fp7 file. No errors found. Remade the solution and the same error. If I create all the necessary files for the application and the whole thing works fine prior to using developer to create the solution (as in all files found and everything working OK) doesn't it stand to reason that the solution would work also? And why is it that when I create the solution all files including tickets.fp7 appear in the solutions folder?

Stanley, I really appreciate your help with this.

Thanks

DJ:

This is very strange indeed. Can you try all this on a second computer? Otherwise... are there any custom functions being used? Any plugins? Obviously I'm reaching for straws here.

-Stanley

No second computer and no custom functions or plugin being used.

Thanks for the help Stanley, nut I think we are fighting a battle that has no winner. I think I am going to try and rewrite the solution to specifically use just the tickets database then compile to see if I get the same eror messages. Thanks for all your help.

One more thought: If there is another file (non-filemaker) named "tickets" in the documents folder, it could cause problems for filemaker automatically opening a file with that name. Although I haven't seen this yet in FM7, I did confirm this happens in FM5/6 with a launcher file opening a remote file.

Thanks Ender, but I only have the databases in the folder.

Well I finally found the answer. Not sure why but I noticed that I had capitalized all of the names of my databases except for the tickets.fp7. Changed it to an uppercase T (which I think Developer 7 was stubborn about) and re-ran the Developers Utility to create my solution. It worked like a charm. I can't believe that this was the error that was making my life hell.

Stanley, I should have paid a little more attention to you and your suggestion of where my files were pointing. It was pointing to the tickets db and not the Tickets db. I bow to your superior knowledge.

Thanks everyone for your help, and when given choices by filemaker, accept them and don't change anything afterwards.

DJ:

It's always the simple things, isn't it. The clue was in the message you were getting; I should have explicitly suggested a file-name problem, but only hinted at it. Glad it's worked out.

-Stanley

Are you actually using the extension .fp7 in your solution? Try .XYZ or something. (Just another straw to clutch at.)