>>
>Thank you for a well-stated and presented synopsis of the current state of things. Much better than "RVs are lousy". <g>
><
>
>My well-stated synopsis nothwithstanding, RV's are lousy...< vbg >....It's just that now, you have some basis for why they are lousy...< vvbg >...
>
>< JVP >

John.

*chuckle*

Well, I can see you are entirely unrepentant. <g>

With the whole notion of 'statelessness' RVs don't make a whole lot of sense anyway, notwithstanding the times you have a hard-wire connection. Also, with ADO being able to pass around a universally understood data format (VFP being the ugly stepsister <g>) I think that MSFT just about has it right.

That's also why I am intrigued with Queued data.

As far as the RV v SR/SPT speed issue, well, I think both you and JR (and others too) all have great points. It's a matter of the larger issues IMO that drive the path one should choose.

I am at the point where I always design my data to eventually migrate to SQL. Quite frankly, if I was going to deal with terabytes I'd most likely ditch SQL for DB2 or Oracle on UNIX. Unix is so much more stable than W2K right now; again, notwithstanding the tremendous advances MSFT has made with it. Most folks who have a background in PC development don't have a clue here. Some businesses, if the O/S they are running or the computer they are running the O/S on, should they fail more than once at all yank the offending O/S or computer. Downtime, crashes or reboots are simply unheard of.