maillist@pvxplus.com

Message: previous - next
Month: January 2002

RE: [Pvx] *OOP straw poll

From: Terry Bauer <terry.bauer@...>
Date: Thu, 17 Jan 2002 14:55:11 -0600
Jeff,

Take it from someone who is currently struggling with a big client (75+
users now) and an application system that was constructed for far fewer
users.  We have update routines that need to lock files in order to update
records (can't run that update now .. the order entry folks are busy) ...
somebody trying to put an item on a contract (requires updating qty on order
field) ... can't somebody upstairs is maintaining that record (EXTRACTed)
... only they went to lunch without getting off that record ......

So, you are far better off constructing your class object to open the file
only when necessary ... extracting records only when necessary .... etc,
etc, etc ....

If your class object comes across a "busy" signal, it can politely present a
message ... such as:

	UNABLE TO COMPLY!
	This record has been assimilated!

;-)

Terry Bauer
Business Computer Systems
San Antonio-Houston 
terry.bauer@...
http://www.bcs-tx.com


> -----Original Message-----
> From: Jeff Johnson [mailto:jeffj@...]
> Sent: Thursday, January 17, 2002 2:42 PM
> To: Providex List
> Subject: [Pvx] *OOP straw poll
> 
> 
> This is really an opinion question:
> 
> I use an object class definition to maintain a customer record.
> 
> Currently, on_create logic opens the customer master file and it stays
> open until on_delete.
> 
> If customer records are opened for varying times, sometimes 5 seconds,
> sometimes 5 hours, would it make more sense to open the file, read the
> customer master info, close the file and wait until I need to 
> write back
> to open the file again?
> 
> Like I said, purely an opinion question, respond to list of private
> email if you think this is too much bandwidth.
> 
> Or don't respond at all, it's a free country after all! <g>
> 
> Thanks to all those who do share an opinion though,
> Jeff
> 
> 
> 
>