AnsweredAssumed Answered

vrf records and datasets

Question asked by VRFuser on Jun 27, 2008
Latest reply on Jun 27, 2008 by VRFuser
It's that collect, store & simultaneously display thing. You're right, a database certainly would cure the problem. In fact, if the dataset is going to get huge it would be a much better idea. Would also really help crank up efficiency too.

Then again, sometimes a minimalist approach is enough of a demo to get the check   Plenty of time to worry about a database after the gas tank is full!

My my. Three years ago I would have said, "...after there's bread on the table."
-SHAWN-

> -----Original Message-----
> From: Warren, Rufus [mailto:Rufus.Warren@Herley.Com]
> Sent: Friday, June 27, 2008 3:23 PM
> To: VRF
> Subject: RE: [vrf] records and datasets
>
>
> Shawn,
>
> I'm not sure what you guys are trying to do, but it looks like someone
> needs to use a data base with multiple accesses.
>
> Rufus
>
> -----Original Message-----
> From: Shawn Fessenden [mailto:shawn@vrfarchive.com]
> Sent: Friday, June 27, 2008 4:14 PM
> To: VRF
> Subject: RE: [vrf] records and datasets
>
> I don't think this is going to get you there.
>
> Basically, I see two problems. One is synchronization. You've got two
> threads trying to access the same file. VEE uses one file pointer for
> each unique file. IOW, there's only one file pointer for both files,
> so when the threads go out of sync something is going to break.
>
> Second is "clear file at open". Every time this file is opened it's
> cleared.
> Certainly not what you want.
>
> What you need IMO is a client/server architecture. The server collects
> data & writes it to an accumulator file and the client reads  &
> displays data.
> Two separate programs. Two separate file pointers.
>
> Unfortunately, you can't use sharing so file access has to be guarded.
> In
> VEE terms, it's probably simplest to put an error output on the file
> access objects & simply delay for a short period when you get a
> sharing violation.
>
> If you expect this to run for a long time error pins can be a problem.
> When
> I ran across this I got roughly 300,000 error pings before VEE lost
> it's cookies.
>
> If you want to use API functionality directly, you could easily do the
> whole thing in one program but then you wouldn't be able to use
> datasets, so that might be more trouble than it's worth.
> -SHAWN-
>
>
>
>
> ---
> You are currently subscribed to vrf as: Rufus.Warren@herley.com To
> subscribe please send an email to:
> "vrf-request@lists.it.agilent.com"
> with the word subscribe in the message body.
> To unsubscribe send a blank email to
> "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list,  email "vrf@agilent.com". 
> If you need help with the mailing list send a message to
> "owner-vrf@it.lists.it.agilent.com".
> Search the "unofficial vrf archive" at
> "http://www.vrfarchive.com/vrf_archive".
> Search the Agilent vrf archive at
> "http://vee.engineering.agilent.com".
>
>
>
> The information contained in this message may be confidential and
> legally privileged. If you are not the intended recipient of this
> email and its attachments, you must take no action based upon them,
> nor must you copy or show them to anyone.
> Please contact the sender if you believe you have received this email
> in error.

>
>
>
>
> ---
> You are currently subscribed to vrf as: shawn@vrfarchive.com To
> subscribe please send an email to:
> "vrf-request@lists.it.agilent.com" with the word subscribe in the
> message body.
> To unsubscribe send a blank email to
> "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list,  email "vrf@agilent.com". 
> If you need help with the mailing list send a message to
> "owner-vrf@it.lists.it.agilent.com".
> Search the "unofficial vrf archive" at
> "http://www.vrfarchive.com/vrf_archive".
> Search the Agilent vrf archive at
> "http://vee.engineering.agilent.com".
>
>

Outcomes