Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. peteraharrison

    Memo field replace reports disk full error

    In the extended version (2.6 (X)) the maximum string length is 2 gigabytes rather than the 64 kilobyte limit in the regular version. This can easily be verified by entering a few bytes into memo field and then running the line &quot;repl <memofield> with <memofield> + <memofield>&quot...
  2. peteraharrison

    Best version (or patches) of FoxPro 2.6 for DOS

    Ramani, Once again, many thanks for your timely and effective assistance. Peter
  3. peteraharrison

    Best version (or patches) of FoxPro 2.6 for DOS

    We are using &quot;FoxPro 2.6 (X) (c) 1989-1994 Microsoft Corporation&quot; in a production environment. I have seen several mentions of 2.6a on this board and also occasionally come across references to various &quot;patches&quot; to resolve other bugs in the program. Can anybody (or bodies)...
  4. peteraharrison

    Memo field replace reports disk full error

    Ramani, Thanks for the input. We are actually running about 35 simultaneous instances of a Foxpro application in separate NTVDM domains on each of many servers. Each of the servers has 512MB of memory. We do use MEMLIMIT - essential, because without it, the first instance of Foxpro will claim...
  5. peteraharrison

    Memo field replace reports disk full error

    When using a memo field to store incrementing history, the program reports a &quot;disk full&quot; error when replacing <memofield> with <memofield> + <newstring>. When this occurs the <memofield> content is usually 64k or more and the added bytes are typically a few tens or a few hundreds of...

Part and Inventory Search

Back
Top