Re: Fujitsu ADO Data access guidance needed

Pete Dashwood wrote:
"Robin Lee" <robinlee@xxxxxxxx> wrote in message
ADO to access Microsoft SQL server, under Fujitsu PowerCobol v6.1...
Some years ago I recall that I used embedded and SQL and ODBC ...
I saw a post here stating that ADO is better.
I've used the samples provided with the AdoDataAccess control ...

Then you will know it is quite OK to use it. (I disagree with Frederico on this; I've used it a number of times and had no problems with it.)

Thank you for that reassurance. I am after all still fairly new with ADO, having only some exposure to it in VB.

I find embedded SQL via ODBC is still the way to go...

I had pretty much assumed I'd be sticking with embedded SQL after seeing some of Frederico's code. (Thanks Frederico for your response but I need to keep this as simple as possible).

Having said that, there is nothing to stop you creating an ADO object through the COM interface and then using ADO commands to access whatever you want. The Fujitsu provided control does this, but shields you from it.

I had seen this referenced in the Fuji docs and intend to explore it.

I'm hoping to come up with some simple code to perform typical COBOL data access along the lines of traditional START KEY/READ NEXT (UNTIL).

There seems to be some confusion here... These are COBOL file system operations that really have nothing to do with Relational Databases. You stated you want access to a SQL Server DB. You can certainly "mimic" these operations against a RDB using a cursor, or a result set if you use access via COM, but it is probably best not to think in these terms as it is tying you to COBOL rather than to your data access needs.

I realize that RDB's do not store (nor access) data in the sequential manner which we may be accustomed to in traditional ISAM databases. Most of what I need to do is to extract records of a certain value or within a certain range. In ISAM that would be START KEY NOT LESS THAN and PERFORM UNTIL (greater than), and in SQL SELECT - FROM - WHERE - IN .... something along those lines. From there I will likely build an ISAM workfile, so sequence of the RDB data is not important. And the volume of data is not tremendous so ODBC/SQL will likely be adequate.

> Without more idea as to what you are trying to do, it is difficult to be
specific. If you don't find what you want, mail me privately.
Pete.

Thank you Pete. I will do some experimentation and contact you only if necessary. And thank you both for your replies to my inquiry.

.

Relevant Pages