>>Hey, I've seen that too. It occurred when I was using WSH or G. Tasker's lnkfiles.dll, I can't recall which - but I didn't have something set correctly. Are you using something to install the icons programmatically?
>
>No, he's using the runtime, and has not issued a RESOURCE=OFF in CONFIG.FPW, or specified a Starts In directory for a shortcut, or the executable is being launched in the Desktop context, and CONFIG.FPW does not point to explicit resource files, so it makes an empty FOXUSER in the Starts In, in this case, the Desktop context. Without full VFP or another app to handle the .DBF or .FPT file extension in the registry, Windows uses its default icon.

You're right - it was sort of a related coincidence that I got the same result using WSH (I believe it was) before I had figured out how to assign the Startup directory.