Where are the DLL's

[SteveB]

The Developer Tool will create your bound solution with an EXE file that should be used to start the application, and 1 file for each file in your solution. In addition, it will create a bunch (approx 12-20) DLLs that must be included in the same directory as your solution. If you are using any plugins, you'll need to copy them into a System folder that is a sub-folder under your solution folder.

If your not getting the DLLs, run the dev tool again and closely watch what it throws up on the screen since it names the folder with its own convention, uless you do something to prevent it.

Although some of the DLLs might not be needed in your solution, like the spell checker, they still must be included.

If you've got multiple files in your solution, be aware that FM will allow the user to start up whatever he's clicked on NOT the EXE which I think it should. You can fix this but it's a bit of a pain.

Steve

[Bill Jaynes]

Thanks Steve,

You said they were there and I kept looking. It was a case of Folder Options (w98)"Do not show system files"

Bill

[Bill Jaynes]

Hello,

I'm reading the fine print to ready my solution. I think FM5 is saying I should see the DLL files in my solution folder after running the Developer tool. The solution seems to work but the DLL's aren't visible

Also interested in knowing from someone who's done it, what exactly to copy over from FMP DEV 5 in Windows. Is it just that whole System folder.

Thanks for your response

Bill

[Anatoli]

RE: If you've got multiple files in your solution, be aware that FM will allow the user to start up whatever he's clicked on NOT the EXE which I think it should. You can fix this but it's a bit of a pain.

Start every file with "start" script pointing to the correct starting script in correct file.

[SteveB]

What Anatoli suggests works, but it has an unintended consequence: You'll never be able to get into those sub files directly...your main will ALWAYS start. The way I fixed that is to put a file in my folder that the startup checks for, and if found exits the rest of the startup script so I stay in the current file. Obviously, you would never ship this file with your solution.

[DaleF]

quote:

---

Originally posted by Steveinvegas:

What Anatoli suggests works, but it has an unintended consequence: You'll never be able to get into those sub files directly...your main will ALWAYS start. The way I fixed that is to put a file in my folder that the startup checks for, and if found exits the rest of the startup script so I stay in the current file. Obviously, you would never ship this file with your solution.

---

Steve, thanks for this tidbit - nice tip!

[ August 22, 2001: Message edited by: Dale ]

[Anatoli]

Steveinvegas got *****

[Vaughan]

Heh heh!

When I first read this I thought Anatoli was being uncharacteristically rude!

(...trying to think of naughty words with five letters...)

[Anatoli]

Vaughan!

I will never! And believe me or not I do try to be always nice.

In this case I appreciated the fact, that Steveinvegas build something better, then was my first idea!

I am proud when I trigger something positive.