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

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

Recommended Posts

Posted

I develop in OSX Lion and produce a runtime in Windows Vista.

I am running FMaker 11 04 ADVANCED.

The OSX source solution runs without any security or login requirements.

After I produce my runtime application in Windows, when I startup the .exe file

I get this dialog message: " Please enter your user name."

It doesn't matter what name, if any, I enter. Everything runs normally after that.

Question, "Why is that dialog appearing in the runtime but not in the source app?

Posted

This only happens the first time the runtime is run. It is the same when FileMaker is installed and run for the first time.

Posted

This only happens the first time the runtime is run. It is the same when FileMaker is installed and run for the first time.

Right you are! Do you know the reasoning behind this 'feature'? Is there some way to turn it off so that it doesn't happen at all?

Thanks

Posted

I don't think it's a Window registry thing. I think FM needs to populate the User Name value in Prefs (a value I never use).

Posted

Inclined to agree Barbara, but it still doesn't happen on Mac. I tested generating 2 runtimes - one with "System" as the user in prefs, then a blank name. The runtime does not ask for a user in either instance.

  • 1 month later...
Posted

possible that the mac version is able to pull your OSX username and windows version can't. I haven't been able to figure out a way to kill this either but it's only once so not a huge deal really.

This topic is 4763 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.