Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

Launching FM5.5 from file locks me out


Oyseka

This topic is 7834 days old. Please don't post here. Open a new topic instead.

Recommended Posts

This is wierd! A system I have developed over the past four years, which has been running quite happily, suddenly won't let me modify a record if launched from the file. When I launch from the file I get a message that I do not have sufficient access priveledges. If I launch the application (FMP 5.5) and then open the file it works OK.

Link to comment
Share on other sites

suppose you are working on MacOS X.

See post

http://www.fmforums.com/threads/showflat.php?Cat=&Board=UBB19&Number=61642&page=0&view=collapsed&sb=5&o=&fpart=1

it occured on my Mac (OS X 1.2.5, FM 6.04) as well. You are not alone.

What's worse, holding to option key while launching (to specify developer password) does not work.

As a work around, I created a launcher file which now opens the main file by "Open" script step, then closes itself.

Link to comment
Share on other sites

No the file is closed. While the addition of one extra mouse click is no great deal, it is the concern that something fundamental has changed in the structure of the file. Sorry by he way I was innacurate in that it is Filemaker Developer 5.5 not FMP.

Link to comment
Share on other sites

suppose you are working on MacOS X.

See post

http://www.fmforums.com/threads/showflat.php?Cat=&Board=UBB19&Number=61642&page=0&view=collapsed&sb=5&o=&fpart=1

it occured on my Mac (OS X 1.2.5, FM 6.04) as well. You are not alone.

As a work around, I created a launcher file which now opens the main file by "Open" script step, then closes itself.

It occurs on 10.2.3 and 10.2.5. The worry is not knowing what has changed to make this occur. The database was first developed in FMP 4 under OS 7.6 and was at that time accessed via the launcher. The entry into the system has always been via the file and not from within the application. As this is happening to you under FM 6 that rules out the upgrade to resolve it

Link to comment
Share on other sites

There are serious problems with OSX and Filemaker.

When Apple figures out they've created this monster, they'll get around to fixing it, but until then, we just have to be really, really annoyed.

Let both Apple and Filemaker ('cause Apple owns Filemaker) know that we're "really, really annoyed". If enough of us report this, they'll fix it faster.

Link to comment
Share on other sites

This topic is 7834 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.