Man this is a nasty bug!!!! The only work around that I could come up with was to split up my listbox items into cursors and setup buttons for the user to select the group (ie. A-D,E-H,I-K, etc.). The user then clicks on a button that fills the list with all items starting with that letter. It works but I hate it! And I still get memory errors from time to time even though my biggest list is only a little over 400 items! I'm running a Pentium Pro 200 with Windows NT 4.0 so I'm wondering if the faster the computer the lower the number of items that will cause this memory error. Geez.

>Do you know some workaround about the problem reported by MS describe below ?
>Any third-party library from some gurus ?
>
>Many thanks for your attention,
>Patrick
>
>===================================================================
>
>PRB: Insufficient Memory in FoxPro for Windows on Fast Computers
>
>Last reviewed: October 27, 1997
>Article ID: Q171047
>The information in this article applies to:
>
>- Microsoft FoxPro for Windows, version 2.6a
>
>on the following platforms: Windows NT, Windows 95, Windows 3.1x
>
>SYMPTOMS
>
>Working programs in FoxPro 2.x fail with "Insufficient Memory"
>when run on newer, faster computers with clock speeds
>greater than 150 MHz. This problem applies to both screens with
>list boxes and queries, but this article addresses only the
>problem with FoxPro screens.
>
>The "Insufficient Memory" error message may also occur while in
>Filer when changing to a local(not network) directory
>which contains a large number of files.
>
>The failure also happens on both MMX and non MMX Computers. This
>error does not occur in FoxPro For MS-Dos.
>
>CAUSE
>
>The current fast computers were not available for testing when
>FoxPro 2.x for Windows was initially released. Microsoft
>FoxPro for Windows, 2.x does not always work with list boxes
>populated from tables with more than 600 records.
>
>RESOLUTION
>
>At this time Microsoft does not have a good workaround; however,
>the following are options to consider:
>
>1.Upgrade the application to Visual FoxPro 3.0 or 5.0.
>
>2.Turn off either CMOS cache (slow) or CMOS turbo mode (very slow).
>
>3.Reduce the number of records to be displayed in the ListBox (under 600).
>
>4.Run the FoxPro applications (app) and executables (exe) on a slower computer.
>
>STATUS
>
>Microsoft is researching this problem and will post new
>information here in the Microsoft Knowledge Base, as it becomes
>available.