BorlandTalk.com

Taras Bendik · Guest

TADOConnection, TADOQuery? Where are they?
There is only TADOConnector, but no examples how to use it. How to use
generic Ole db connection ?
There is no BDP fo Informix? How to make application with Delphi 8 and
database server that is not (Oracle,Interbase,MS Sql, DB2) ? I can use
ADO.NET but then RAD have no sense in Delphi.

Michael Rodriguez · Guest

"Taras Bendik" <taras at ultra com mk> wrote

Isi Robayna · Guest

Same Here...

I am hoping that they will do a maitenance update with the ADO support.
(please???)

Isi Robayna

"Michael Rodriguez" <mike (AT) nospamforme (DOT) com> wrote

John Powell (Borland) · Guest

George Christoforakis · Guest

oops, our whole c/s application is based on ado....well at least one version
of it....
well, let's hope that borland will import it in d8.

George Christoforakis.

"Isi Robayna" <isi@!NO_SPAM!healthcaremanager.com> wrote

Dennis Passmore · Guest

You can convert your Delphi 7 Adodb application to Delphi 8 using a Interop Assembly that
you can create using Tlbimp.exe which is installed with the Microsoft .NET SDK. Open a
command prompt into:

C:Program FilesCommon FilesSystemado

and then execute the following statement:

tlbimp msado26.tlb /out:adodb.dll /namespace:Adodb

This will produce a adodb.dll interop Assembly that you can added to your Delphi 8
application and then access your database using the same native adodb syntax that you did
in Delphi 5-7.

Here is a sample of working Delphi 8 code:

procedure TWinForm.Button1_Click(sender: System.Object; e: System.EventArgs);
var
daTitles: OleDbDataAdapter;
dsTitles: DataSet;
Conn: Connection;
rs: RecordSet;
sql: string;
i: TObject;
begin
Conn := ConnectionClass.Create;
Conn.Open('Provider=SQLOLEDB.1; Integrated Security=SSPI;'+
'database=Pubs; DataSource={local}', '', '', -1);
SQL := 'select title_id, title, type, price from Titles ';
rs := Conn.Execute(SQL, i, 0);
daTitles := OleDbDataAdapter.create;
dsTitles := DataSet.create('Titles');
daTitles.Fill(dsTitles, rs, 'Titles');
DataGrid1.SetDataBinding(dsTitles, 'Titles');
Conn.Close;
end;

I will post the entire project to the .attachments newsgroup. The "ADO_Example.zip"
project was created on a WinXP system so if you loaded it into Delphi 8 running on a Win2k
system you may have to manually updated the Project1.dpr and Project1.cfg files to correct
the references to "C:Windows" which would change to "C:WinNT".

Dennis Passmore
Ultimate Software, Inc.

Del Murray · Guest

Reading this is so scarey ... why does the microsoft world have to produce
such chaos when move "up" in technology ??? Makes me want to go back to
cobol and mainframes.

Dennis Passmore · Guest

I do not think that backward compatibility is "scary" but just something that had to be
provided as a transistion effort. The old ADODB library is "unsafe code" so the only way
to access it is by using a "unmanaged" COM interop interface.

Dennis Passmore
Ultimate Software, Inc.

Michael Rodriguez · Guest

<Dennis Passmore> wrote

Johannes Lindthaler · Guest

Good day,

I agree with Mike because all our projects use ADO. If one believes Borland,
the main reason for upgrading is a smooth migration. Otherwise it is cheaper
to buy VP.Net.

Before buying Delphi 8 Enterprise, I did not realize that there is no user
manual coming with the software. Unfortunately the Delphi 8 specific help
file is pretty shallow and the rest of the help file is copied directly from
Microsoft's .NET languages, which has only limited use if one looks for
Delphi specific information. I'd hoped that Borland would have some
Delphi.Net specific newsgroup by now, but so far I have not found it (if it
exists). Needless to say that I was really exited to finally receive Delphi
8, but so far I have faced a lot of frustration to really get going due to
errors, the lack of documentation and the lack of really useful examples.

Today I ordered the "Delphi.Net Developer's Guide" from Xavier Pacheco and
hope that Marco Cantu, Darakhvelidze/Markov and Steve Teixeira will also
soon release one of their invaluable books.

Johannes

"Michael Rodriguez" <mike (AT) nospamforme (DOT) com> wrote

David Wilcockson · Guest

Absolutely. Borland often state that Delphi allows you to 'move into the
future - without abandoning the past' - on the face of it, not this time!
We now seem to be stuck on Delphi 7 due to lack of support for the ADO
components in Delphi 8.

David

"Johannes Lindthaler" <hlindthaler (AT) marinexchange (DOT) com> wrote

Viatcheslav V. Vassiliev · Guest

With COM interop you import COM type library and use its wrapper (similar as
you do in Delphi for Win32). Wrapper is managed and ADODB is included in
..Net framework as primary interop assembly. But ADODB can not be used with
db-aware controls. To use ADODB with db-aware controls you should use
System.Data.OleDb.OleDbXXX objects (OleDbConnection, OleDbCommand etc.)

//------------------------------------------
Regards,
Vassiliev V. V.
http://www.managed-vcl.com - using .Net objects in Delphi + ADO.Net
http://www.oledbdirect.com - The fastest way to access MS SQL Server,
MS Jet (Access) and Interbase (through OLEDB)

<Dennis Passmore> ???????/???????? ? ???????? ?????????:
news:2m76vvgs0i530tqhnpb7dghqs9qljt2fie (AT) 4ax (DOT) com...

Bill C · Guest

G'day all
Having just developed my first app using D7 Pro and ADO, I am disturbed to find that D8 does not have these components. I had intended to buy D8, but certainly not now. NO customer I know is yet interested in .NET
Borland please take note!
Cheers
Bill

"David Wilcockson" <dnw (AT) librios (DOT) com> wrote:

Del Murray · Guest

It seems that Borlands strategy has become a cousin to Microsoft. Change
everything and release an incomplete product. Promise the next release will
take care of it all. This is a great misstep for Borland and I hope they get
it corrected soon. I wont touch a .Net program because I dont think I should
have to load my computer or my clients with the .NET Framework .... another
thing to contstantly migrate and install on client machines and then
maintain. And who knows what problems it will cause with stuff that was
working just fine before I install it ? It is almost as bad as the old way
one had to install basic programs 5 years ago. They almost got it to where
you can just send an "exe" to your client and then they thow up the
"framework" road block. I swear, I 'm going back to mainframes.They may not
have mouses but then everyone is complaining about all the clicking and
wrist fatigue anyway ...

Dennis Passmore · Guest