Hi,

I have a read only database for CD distribution that I want to launch directly to the first layout. Problem is I always get a dialog box on startup asking for a user name. I haven't defined any access privileges, users/passwords, so I don't know why its asking.

Thanks,

Randy

Set the file options to automatically enter a password.

Hi, thanks for the reply.

I just created a password "guest" with limited priviliegs and under the "edit/preferences/document" menu I entered "guest" in the "try default password" field. Is that where you meant? I then built the runtime solution (FM6) and it still asks me for a user name. Only the first time launching mind you, but I don't want to see it at all.

I've never really tinkered with groups and passwords much, so I'm obviously doing something wrong.

Thanks.

Hi, Randy. Is the attached an example of the box you're talking about?

If so, the value of this is typically controlled by the Windows registry and is stored so that the next time the solution is opened the user does not have to enter it. You can find the registry key at HKEY_CURRENT_USERSoftwareFileMakerYourSolutionName6.0Preferences in the [user Name] value.

For whatever reason, this value is not sticking (obviously). Do you have any sort of software running on top of the OS, such as ZenWorks?

HTH,

Jerry

--i feel a visit from DykstrL coming on--

Hi Jerry,

Yes, your .gif is dialog box I want to avoid. Don't know what ZenWorks is so I'll google it.

The Reg keys are interesting. I just looked and I see a whole ton of them created from my testing. Upon first launch the preferences aren't there, hence the dialog box. The issue is still to avoid the dialog box altogether when running this off a CD for the first time on a new computer.

Thanks,

Randy (XP Dev6)

If you don't know that you have Zenworks or something similar, chances are good that you don't. It's more than a utility, it's a pretty significant piece of software.

Just to clarify-- when you run the program for the first time on a given computer, you see this dialog box. (This is expected behavior for a runtime.) Do you see the same box again the next time you run the program on the same computer?

If it only occurs once per computer, you could prevent this box by creating the reg key at the same time the program is installed. If the [user Name] value is present (even if it is blank), the user will not be prompted to enter a user name. There are several methods for doing this, probably the best of which is to invest in packaging software like InstallShield or Paquet Builder.

J

Hi,

Correct. First time I get the dialog asking for user name. Second time its okay. So its the old "that's the way it works"? What a strange behavior for a runtime solution, why does it need a user name at all? Why can't something scripted automatically like the password? I have Wise Installation Systems so I can build an installer but it would be nice if it just ran from the CD too.

Cheers,

Randy

Doesn't Wise Inst System let you specify registry keys to be added/changed at install time?

I use Tarma Installer and the Pro version has this facility.

Hi, Randy. I had an idea on this that might be helpful. You can create/edit/delete registry values through the use of a .reg file. For example, if you had a file named username.reg whose contents were:

launches your program from the shortcut. This would fill in the user name for them every time without user intervention. The batch file would look something like:

Windows Registry Editor Version 5.00



[HKEY_CURRENT_USERSoftwareFileMakeryourSolution6.0Preferences]

"User Name"="Anyuser"

this would, when run, populate that registry key with the string "Anyuser."



I assume you have a shortcut on the CD that users run; maybe you could instead have them run a batch file which (A) starts username.reg and then (

REGEDIT /S d:locationOfDotRegFileusername.reg

start d:locationOfShortcutshortcut.lnk

(The switch /S runs the reg file in silent mode, so that the user does not get a horrifying message that says "Your registry is being changed.")

One potential pitfall of this approach is that it could cause the user's A-V to go nuts.

J

Hi again,

Yes, Wise Installation Systems will let me create a registry entry. So I could build an autorun with Wise that would write the registry if it doesn't exist and then launch the application. Or with a batch program as you mention above.

One drawback could be that companies that run this on a network may simply not allow system level modifications. I think at this point the client will live with it as is. Though it still irks me that FM needs to know this at all.

The funny part about this projecto for me is that I choose Filemaker to do this project in stead of my usual application ... Macromedia Director. I've been wanting to do a Filemaker project for awhile and this one fit the bill. A quick little database that you can search, browse, print and less programming. No multimedia elements and it works great, but all the things I take for granted with Director are clunky with Filemaker. ie, centering the window on screen and blacking out the rest of the monitor. Kiosk mode in FM is a real misnomer (IMHO).

Cheers,

Randy