Originally posted by Mike_Carr:
Thanks for the help Ian. Very muchly hugely greatly appreciated. I will name my first-born child (boy or girl) after you if you can help me work through this.
I would be flattered
Im very happy just to have you using our new Max Talk site.
Im afraid this is not a simple problem, youll need to cross possibilities off one by one. Heres a few more thoughts
If you followed Multiactive settings for your btrieve you should be OK. Again it sounds like youve done all the right things.
I think its unlikely to be the cause of this problem, but you should avoid filepaths to your data that contain spaces. Preferably keep to 8 characters or less on a mapped drive.
I suspect were looking for something less obvious like maybe a PC with a really nasty BIOS powersave routine that cuts off btrieve mid conversation. (These usually just cause nasty messages to appear in Maximizer like
Sunday OK when the system comes back on.) Possibly its just a rouge PC or network card.
Though again Im not sure its the cause, try to ensure all your network cards use the manufactures
driver. Avoid loading NE2000 Compatible.
It may be worth setting the following registry entry on all machines just to ensure that Btrieve does not even dream of IPX/SPX.
HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Communications Requester\Version 6.15\Settings
The last time I saw a problem similar to this, it was often discovered first thing in the morning. Is there any pattern at all to your crashes? What other things were users doing at the time?
By all means email a Dr Watson File to firstname.lastname@example.org, though I agree most of contents is hard to get real information from!