December 27, 200520 yr I need some advice . . . I've got a 17 table system that has gone through several iterations during the development cycle. I've finally reached the stage where I want to produce a Kiosk version using the developer. My problem . . . in earlier versions of the tables have relationships that do not exist in the current version. However, when I compile the tables I always get an error because the compiled solution is looking for a previous relationship. I've removed all the old versions from my system and I've reviewed all the tables to be sure that I don't have a rogue relationship that still exists . . . I didn't find any. The problem still occurs Anyone have any ideas of where FileMaker is looking for this information and giving me bad links?
December 27, 200520 yr The 1st question is: your profile shows FM 5 Developer. Is this true? Please update your profile if it isn't. Steve
December 27, 200520 yr I believe that version 5 Filemaker stores references that are not visible. This is especially noticable after you convert a file to v8...you'll see all kinds of old references.' I don't have any answers except rechecking everything again. You 'might' be able to find the problem with Analyzer from Waves in Motion, or Brushfire from Chaparral, but neither will run in version 8. I'd sooner spend my money on upgrading to v8. Steve
December 27, 200520 yr Author Thanks Steve . . . I'll recheck everything again and give er another go. Otherwise, I'll wait for 8. Happy Holidays
December 28, 200520 yr I've had that same problem with V6. Drove me nuts. It eventually got fixed when I repeatedly re-entered my relationships. :hair: Edited December 28, 200520 yr by Guest
March 18, 200619 yr One thing that REALLY causes issues. Make umpteen sure there are NO OTHER COPIES of the files on your machine or any linked machine as you edit the relationships. Really. This caused me major headaches. I thought having a backup was a good idea, but ended up using stuffit to keep it from interfering.
Create an account or sign in to comment