Question ODBCCommandBuilder generating incomplete SQL

[BGourdie]

I'm having the same trouble as this person (no resolution): http://www.progresstalk.com/threads/openedge-net.94524/

I'm making a C# .NET program that can perform CRUD functions through ODBC on any one table in the Progress database as a quick and dirty maintenance tool.

Attaching an OdbcCommandBuilder to an OdbcDataAdapter creates the requisite Update() commands (insert, update, and delete) at runtime, but they are mysteriously half-baked and sometimes ridiculous when using Progress's ODBC driver. Is this a limitation?

This problem isn't well-documented around the web, so I assume something is wrong with our database or no one uses the OdbcCommandBuilder class with Progress.

The Get It Done solution is what I'm working on: build my own SQL statements; however, I'd really like to know why Microsoft and Progress aren't cooperating.

Using Progress version 10.2b on Windows 7.

 

[jdpjamesp]

I was going to suggest you create a thread on the Progress Community but I just found the one you already have. Not sure what else to suggest, other than raising a support call with Progress.

 

[RealHeavyDude]

Before you blame me: I know that does NOT help!

But, does Microsoft even know that Progress does exist?

Heavy Regards, RealHeavyDude.

 

[TomBascom]

Keep in mind rule #1 -- Progress is NOT SQL

If you always remember this you will be much happier.

 

[BGourdie]

But, does Microsoft even know that Progress does exist?

ODBC is a standard outside of Microsoft. The idea is that Microsoft does not have to care about who exists, only that their supplied ODBC driver works. To me, it looks like one side is assuming something that the other isn't.

Not sure what else to suggest, other than raising a support call with Progress.

This is my attempt at putting that call off but it's looking more and more like I will have to make it. :<