Executable can't execute

[evan_panagiotopoulos]

I created several standalone applications without a problem. Now I have two simple databases that when i create the executable when i click on them nothing happens!

Now what do I do?

Thanks,

Evan P.

[evan_panagiotopoulos]

Would the length of the file have anything to do with it. The folder is nested pretty deep, about 80-90 characters worth of folders.

I moved the executable closer to the root of the drive and now it works!

I am Confused.

Evan P.

[summergirl]

Hmm, interesting question. I have a client running Windows 2000 Professional who is having a similar problem.

The .exe file will not launch when she double clicks it. She gets an hourglass, then nothing. The .exe, data files, and .dll files are all located in the same folder on her desktop.

I emailed her just the .exe file so we could replace the one in the folder. But when we tried to trash the old .exe file, the computer said it couldn't delete it because the file might be in use. (?)

We loaded the runtime solution on a Win 98 machine and it and launched just fine. I'll send her a new CD, but I suspect I'll get the same kind of problem on the 2000 machine, new CD or not.

Any insight from fellow users? And has anyone had weird runtime problems on machines running Macafee virus software? Windows 2000 OS?

Thanks for any help.

[summergirl]

FileMaker is aware of a launching problem with Dell and DTK machines running Win 2000.

Here's the tech article website:

http://www.filemaker.com/support/techinfo.html

Type in Article #107071 for the fix.

I'm just passing along info from dykstrl Member #1697 posted in the FileMaker Pro 5.5 forum...

Mary Z

[DykstrL]

The other problem with Windows 2000 (and XP) is that if the user does not have rights to install software, the runtime EXEcutable will not register the file extension and either will not run or will try to open the solution file(s) with something else, most of the time as a Word auto-file - which will then associate the extension with Word.

We have had to initiate a message window in our install packages to warn W2K users that they either need to have software installation rights or be logged on as an administrator.

[ November 30, 2001: Message edited by: dykstrl ]