Aleksey,

After a thorough investigation and testing, I found out that there are modules wherein upon activating them and activating another one fires fatal error if running the EXE outside the VFP development environment. In other words, running an EXE alone this problem occurs. But if I run the EXE inside the VFP IDE say DO myexe.exe in the command window, these fatal is not occuring. So it's the runtime exe that have the problem.

Sorry but I can't find where the bucket id is?

>Jess,
>
>What about bucket ID?
>
>Aleksey.
>
>>Guys,
>>
>>Sorry for my delayed reply because I need to attend to my clients on site. One noticeable thing is that computers with 256MB RAM and above rarely encounter this fatal error. In other words, users who have PCs with 128 MBs usually have to close forms before opening another one.
>>It is ironic to ask clients to upgrade their end users PCs into 256MB. And you know what? In a hospital environment, a lot of PCs - especially Nursing stations - don't need to have a very powerful one because most of the time they remain idle.
>>
>>Also, we are not using ADOs or COMs, it's an 2-tier architecture using RVs, SPTs, and lately CAs. To reiterate, it works fine in 7.0.
>>
>>>>Where can I find the bucket ID?
>>>>
>>>
>>>If you sent error report, Application Event Log should have an entry for Microsoft Visual FoxPro similar to this:
>>>
>>>The description for Event ID ( 1001 ) in Source ( Microsoft Visual FoxPro ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 43390951.
>>>
>>>0000: 42 75 63 6b 65 74 3a 20 Bucket:
>>>0008: 34 33 33 39 30 39 35 31 43390951
>>>0010: 0d 0a ..
>>>
>>>
>>>In this example, 43390951 is the bucket ID.
>>>
>>>Thanks,
>>>Aleksey.