Daniel, I dont know the answer but here are some suggestions:


>1) The first one is "Ole server can not be found or executed". a. This closes the app.

This implies that there is no (OLE server) application associated with the BMP file. Is there one?


>2) When they go back in and browse they get an internal inconsistency error in FOXPROW.EXE and we get kicked out.

This means that the indexes are corrupted. See

CDX Corruption Checklist - http://fox.wikis.com/wc.dll?Wiki~CDXCorruptionChecklist~VFP

and

Index Corruption - http://www.craigberntson.com/Articles/kb005.htm


>It appears that Memo field is being corrupted. Is their any way to fix it?

There are several file repair utilities, some for free, some not. For example, see

ATFixDbfFpt 1.5a, all xBases supported. File #9930

and

Crashed tables rebuilder File #9264

and

FoxFix from XiTech - http://www.foxfix.com


>The problems started occuring when they purchased a 2,8 ghz Server with dual zeron processors and 1 Gig of Ram, and three 2.8 ghrz Dell systems with 512 Ram. The Server is running Window 2000 SBS. The workstations are running XP Pro.

See Re: FPW 2.6 with XP or with Win2K Thread #751149 Message #751287


>Additionally, they are having a problem in finding the right OLE or ODBC Driver for the Window FoxPro 2.6.

OLE or ODBC? Search the MS site in the downloads section.


>The fast patch has been installed long ago.

Are you sure? You say they upgraded the hardware.


>Is it possible for a General memo field to get so large that it will cause a internal inconsistency in foxPro 2.6?

There is in VFP a 2Gigabyte file size limit. This might be less in FPW - I am not sure.


>Any ideas what causing the problem? How to get it to stop? and how to fix the General Fields? All information will be greatly appreciated.

A) BMP is a very large file format. If possible change to something more efficient such as JPEG, GIF, PNG.

B) Do not store the files in general fields at all. The general recommendation by UT members is to store path and file names in a char field pointing to images on disk. This avoids so many hassles like this.


HTH