>>>An FPW 2.6 .exe application I've inherited doesn't seem to have a config.fpw (in the directory from where the exe is started or in the project itself). After looking at other messages on the topic, I suspect that may be why I'm receiving a Watcom 386win error (FPW may be using a higher memlimit default). My question is: should I include the config.fpw in the project and rebuild it, or just create one and leave it in the default directory (this is not a standalone executable)?
>>>
>>>Thanks,
>>>
>>>Sylvia
>>
>>Watcom 386 error is difficult to figure out, but to answer your question I would not include it, but just provide it, that way if you need tochange it you can. I have solved our watcom 386 error by informing our users that WordPerfect applications and FoxPro dont seem to get along. If they start up FoxPro first they seem to be OK, but if they start up the WP applications then Watcom 386 rears its ugly head.
>>
>>HTH
>
>Ouch! It sounds as if lowering the Memlimit in your configuration file didn't solve that Watcom problem. WP is the primary application used by the folks who will also use the FPW application, so telling them to fire up that app first is not practical in my situation, and is probably unworkable. Is that pretty much an accepted viewpoint (i.e., that FPW and WP don't get along very well and this is the only work around)?

I dont know if it is the only work around, but so far it is the only one I have found. You might search the Microsoft Knowledge base and see if there are any further references to that error message. Let me know if you find out anything more as I would like to solve this probelm also.