I never thought it was rude of you guys to suggest that RIO was not worth the effort of the challenge when it was suggested during the "let us convert your vfp app to net" campaign of a year ago.

Now you come t the table with an incomplete solution wanting someone to pet your head for "giving it a try"! Inbelievable that I am rude and yet the NET project is incomplete. Totally un beleivable.

I see you still had to compromise - why is the hot tracking always on? I'll download and I'll evaluate - even though it fails the initial challenge assertion that it had to be small enough to comfortably download.

If it has an additional form - then it did not meet the challenge either - but I'll download - you could have made it easier by just internally loading an initial data set into ADO - but now I have will have to mess the ODBC.

I'll download - but I will be upset for the effort should I come to learn that you substituted a "chrome" shifting knob to compensate for a low end transmission.

I believe I already told you it implements the majority of what your application does.
This is where you loose me - there is so little to RIO - whats with the "majority" disclaimer.

With the exception of a load of technical disclaimers and the fact that it is little more than a "loss leader" product to sell SQL backends, it does not seem compeditive with the kinds of interfaces we can develop with VFP.

>With some minor exceptions---
>1. Hot tracking is always on in my version.
Why?
>2. I have an add button on the toolbar
Why?
>3. It demonstrates all the points you make in your app.
We'll have to see -
>
Unless I missed some functionality somewhere it does what yours does.
It's not just what RIO does - Excel or Quick Basic can do that - it's performance. On the outside a "fake" Rolex looks just like a real one.

>
I think its rather rude of you to put a challenge out and not verify whether the apps performs up to your "standards"....
I am going by the reviews already posted.

>
>So go and check it out and let us know.
>
>If it is missing something let us all know and I'll make the changes.
>
>2 weeks later we are still waiting for you.
>
>Rodman