July 8, 200520 yr I did a small test, here: http://www.fmfiles.com/dev2.html ...is an Applescript droplet that I used to use earlier. That contained this code: on run set thefile to choose file convertFile(thefile) end run on convertFile(thefile) tell application "Finder" set creator type of thefile to "FMP7" end tell end convertFile on open (theObject) sortObjects(theObject) end open on sortObjects(theObject) set theinfo to info for theObject if folder of theinfo then sortFolder(theObject) else set theObject to theObject as string set theObject to alias theObject convertFile(theObject) end if end sortObjects on sortFolder(theFolder) set thelist to list folder theFolder repeat with x in thelist set thePath to theFolder & x as string set thePath to alias thePath sortObjects(thePath) end repeat end sortFolder I recompiled it on OS X and made a bound solution ...and apparently the idea still works, and even better now than before because earlier were the ability to turn into layoutmode in the reconverted file crippled. But the investigation is a single stab that might appeare to have other artifacts creaping out from somewhere else. I don't know how this translate to runtimes made on XP!!! --sd
July 9, 200520 yr In reality though, if you simply rename the extension of one of the files of your compiled application back to fp5, fp7 etc, it should open in FM no problem. In FACT!, even if you don't do that, you can still open a so-called compiled version file in regular FMP HTH
July 9, 200520 yr In FACT!, even if you don't do that, you can still open a so-called compiled version file in regular FMP Yes, thats the artifacts I ment.... but in 4dev for mac could you inspect dialogs etc. with resedit and find no-one have have been bothered to remove the networking stuff ...they only put a cork in to prevent the networking to be used in bound solutions. By and large did I never find the binder particular usefull, I've crashed numerous solutions when attempting to localize validation dialogs using tons of hours tweaking with debugger, althoug it can be done when you learn to dissect correctly ...but the profits gained from it is questionable because a lot of trial and err is manditory to get the hang of it. What I try to say here is make the solutions from scratch instead of repairing old stuff. You are likely to have learned something meanwhile a new solutions could benefit from ...it might sound like reinventing the soupbowl ...but no it makes you take care of previous flaws or inaccuracies in you interpretation of the clients wishes. --sd
July 11, 200520 yr Author In reality though, if you simply rename the extension of one of the files of your compiled application back to fp5, fp7 etc, it should open in FM no problem. I've tried on couple of different runtime solutions (created from Fm5 and Fm7) to change extension, but FM can't open a file(s). In FACT!, even if you don't do that, you can still open a so-called compiled version file in regular FMP Can You please tell me what is "compiled version file"?
July 11, 200520 yr The "compiled" version is the runtime file. As normdouglas recommends, you can rename the runtime to have an extension of .fp7 instead of the .usr extension. I just tried it on an XP machine and it worked perfectly. Mike
July 11, 200520 yr I didn't try everything, but I modified a script and defined a new field. The new field was added to the layout. It acts like a regular FM file. Mike
July 12, 200520 yr Author After few small tests - yes, you can do everything from your list. It's look like a regular Fm file.
August 24, 200520 yr I've tried the same thing and it works fine from within FM, but if you create a solution from that file - it won't launch! It's a shame - in my solution the user can save a copy of the database. But then how do you use that file if the database becomes corrupt. I was hoping that would be easier than exporting then importing records into an empty solution.
September 16, 200520 yr open any folder go to tools folder option view and uncheck hide extensions for known files types BE CAREFUL after that when you change a name for example mike.doc to mike1 you must write it mike1.doc
September 16, 200520 yr Newbies Hi all, thx for this. It seems to work for me. I'm under win2000 using FM5.5 renamed a bunch of .usr to .fp5 and it seems to act as regular .fp5 so far. If somethings wrong happens, i'll let you guys know.
September 16, 200520 yr Newbies Hey, sorry for not editing, but my iexplore crash when i hit the button Ok, i have found out that when browsing the application that was compiled back into .fp5 files, i have errors. FM thinks i'm using the version with .usr files. He wants me to locate em. Instead of putting the .usr, i load the .fp5. It works, but it's annoying (as you might guess). Anyone knows how to tell FM that i want to work with the .fp5, not the .usr ? thx :)
October 28, 200520 yr Resetting a file extension on a simple file should not be a problem. A more complex solution may fail to work for a number of reasons. The problem with resetting USRs to FP5 is that the internal pointers (scripts, links, buttons, relationships, etc.) tend to look for the USR file NOT a renamed FP5. Tried this fix a number of times and has always worked. (If you have Developer). Rebind the solution, select FP5 as the file extension. Select "Rename files and update links". You will now have an Fp5 solution where all the children will play nice with others. If you still choose to replace the file extension rather than rebind it is best to replace the file extension in ALL of the files in the solution, then activate every link and script and redirect as needed to the "new" (Fp5) files.
Create an account or sign in to comment