Once upon a time I discovered opener files. That made me very happy as it avioded a number of mouse clicks for users and allowed them to look in the file system for the file they wanted rather than using Open Remote or the Hosts button.

But now I discover that the opener file passes a full set of credentials along with it... I was having even more fun using external authentication to access the user's NT User Name; using it to validate which record they modified or created or were allowed to access, all without having to maintain 90 users in two places.

Anyone know if there is a way around this credential passing?

Grant:

You mean you are using Opener Files to open FileMaker databases directly through the OS? If so, this is a really really bad idea, and will guarantee you corruption and problems. Much better to make the opener file do the Open Remote call for you and open the files via FM Server (or FMP multi-user.) Also, I believe there are no credentials passed (other than the user name, which can be the NT User Name or a custom one - your choice.)

-Stanley

Grant,

So far I've been able to do away with the opener file concept by using a desktop icon that directly opens the hosted file. Try creating a new icon with a target something like this:

fmp7://10.10.10.36/Main.fp7

(I'm doing the syntax from memory but it is something close to that)

Of course subsitiute the IP address of your server and the file that you want to open. I've heard that some folks have trouble with this method but personally I have not. I'm running XP, W2K, and FMS Advanced.

Good luck,

TedS,

Thanks, that is just what I need.

Stanley: no, I am doing what you suggest: using the opener to do the open remote, but because it performs that action, it passes the credentials whcich are not externally authenticated. Since theb opener is not hosted by FM Server, it can't use external authentication

Try having the opener automatically authenticate with a low level access account that doesn't exist in the hosted solution. I believe when it connects to the host and sees that the account is not in the destination file, it will ask the server to authenticate again. I haven't tried this, so let me know if I'm mistaken.

The actual syntax is "FMP7:10.10.10.123filename.fp7". Works like a charm

Ender, you, sir, are correct! I don't think it's really the best bet for me though... I really like the shortcut method since no one need remember any password at all. Nevertheless,a briliant solution...