Kent Belan wrote: > Hello, > I have a client that has been going along great for the last 10 years. He is > now ready to explode. > > We are pushing the 2 gig limit now on the client table and he wants to add > tons more.
(Anticipating flames, I say this softly...) A band-aid approach that may be expedient in your current circumstances: Stay ancient and split the offending table. Many years ago, I had an old-style Fox application (I created in FP [2?] and migrated to FP-Win, then to VFP). It had one table approaching the 2G limit. Since it was only one table, I elected to split it (vertically: fields 1-40 in table A, field 1 [PK] and 41-x in another). It didn't take too long to update the forms and reports. You might even find it just as easy to upgrade some of the data access language to SQL for SPT, or even build a data object for it. That may buy you time to upgrade the application to modern standards without holding the client back while you do. (Flame away, PFers!) Ken _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
