Ed,

> I can only report my own experience.

That's exactly what I am hoping for.

> IBX conversion was a no-brainer. Absolutely no conversion problems; The

TIBDataSet works exactly as I would like. Our

> applications are not extremely complex, about 30 basic tables plus

ancillary tables. They do order-entry/fulfillment and the

> management.

> I could never quite get IBO to work the way I wanted it to work.

What was it you were trying to get it to do that it couldn't?

> I was never interested in replacing my infopower grids nor my orpheus data

edits, so that part of IBO never interested my (and

> it is my opinion that you have spread yourself WAY to thin in the

development of these controls).

Sounds to me like you were trying to convert over to the native IBO stuff
instead of the TDataset stuff. I don't encourage people to do that. IBO's
TDataset stuff is what you should have been converting over to.

> Finally, the IBX documentation answered my questions; where the IBO

documentation usually left more questions to be answered.

IBX's documentation is laughable compared to the amount and quality of
documentation for IBO. A large majority of it is just a lift of other
documentation on the standard components.

> For me the bottom line is that IBO did not do what IBX does.

Such as? If you are going to bring this up and make it a topic of discussion
I expect you to provide the details of your experiences.

> As you know I purchased IBO licenses and gave them a fair test. For
> our uses, IBX fits, and I chose not to try and fit our applications to

IBO's demands.

What "demands" are you referring to? It would seem to me IBX has more
"demands" on the application developer than IBO does. I would like to
explore this with you from your perspective.

Thanks,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com