Jos,

Some other ideas:

1. Can you start the user's program via the command line by switching to the application folder and running your EXE?

2. What are the user's PATH, TEMP, and TMP settings? Anything unusual?

3. Make sure that the MSVCR70.DLL exists either in the user's application folder or in a folder where you are sure that Windows can find it.

4. Make sure that the GDIPLUS.DLL exists either in the user's application folder or in a folder where you are sure that Windows can find it.

5. If you've gotten to this step without any success, try copying MSVCR70.DLL and GDIPLUS.DLL to the same folder as your EXE. Does this make a difference?

6. Has the user's application folder or DRIVE letter changed? Its easy for this to happen as many users have digital cameras or music devices that attach themselves as additional drives which may throw off the drive letter sequence your application expects?

7. Does your config.fpw file explictly mention any drive letters? If so, make sure all these drives are valid.

Finally, have your user go to the command line and type:

C:
CD \
dir *.* /s /od > myfiles.txt

Have your user email the file C:\myfiles.txt and then review the directory entries for folders and files with recent dates (the /od orders each folder by date). This may help you uncover what new applications were installed that the user may not know about.

Good luck!

Malcolm

PS: Would be curious to hear what the problem was when you finally solve it.