|
Hi Jim, et.al. - >If you are adding new fields there are a few ways to go about it, >mostly dependent on the programming language you are using. The >easiest way is to just not pass back these new fields for the old >call. Create a new call that passes back the full records and have >any program that needs these fields call the new procedure. That >way you have to modify only the programs that need it. If you remember from the lengthy discussion on the OpenERP list, one of the possibilities is to use a service program for the I/O and have the service program own the storage for the record, rather than the caller. That way so long as you add fields to the end of the storage, and just pass a pointer to the storage area back to the caller, you don't have to even know what version of the record that the caller knows about. And of course the storage area mapping does not have match the actual file layout. The data doesn't all have to even be in one file. Ken Southern Wine and Spirits of Nevada, Inc. Opinions expressed are my own and do not necessarily represent the views of my employer or anyone in their right mind. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.