Prev: MD5 encryption of a String
Next: RC.exe
From: andrej Terkaj on 30 Mar 2006 12:16
Thanks you quys !

As usually. It was my mistake. A few days ago I upgraded Vo2ADO on the
newest version. But I forgot to rebuild it also in my VO project. Thatsway
programme always broke when initializing AdoServer{}.
Everything works fine.

But I am richer for a new experience. And this experience is, that I can
always have help from a good VO friends.

Thank you once again
Bye, Andrej

"Sherlock" <sherlock(a)sherlock.com.au> wrote in message
news:1143731394.666129.119090(a)e56g2000cwe.googlegroups.com...
> All,
>
> This has a resonable tutorial on the subject with sample code as well.
>
> http://www.devarticles.com/c/a/MySQL/MySQL-and-BLOBs/
>
> Phil McGuinness
>


From: Geoff Schaller on 30 Mar 2006 17:19
Well the thing about this Phil is that we are not talking about you <g>.

Some discussions are like that. Sorry.

Not everyone wants an API approach because it locks your code to a specific
DBMS. This may not suit some folks because they don't want to rewrite the
code for a second client using a different server.

Geoff


"Sherlock" <sherlock(a)sherlock.com.au> wrote in message
news:1143718866.749475.201150(a)g10g2000cwb.googlegroups.com...
> Geoff
>
> Never tried in the first place. When you have a working solution why do
> I need another one.?
>
> Phil
>


From: Phil McGuinness on 30 Mar 2006 18:23
Geoff

For the ODBC approach there are ADO users and the techniques are shown as
well.

So we have the API way.. and their is ODBC way and ADO.NET providor as well.

Lots of options ?

Phil
--



From: Geoff Schaller on 30 Mar 2006 17:33
....and none of these help with a VO app using ADO right now <g>.

Thanks for the confirmation.


"Phil McGuinness" <sherlock(a)sherlock.com.au> wrote in message
news:e0hlp7$8b9$1(a)news-02.connect.com.au...
> Geoff
>
> For the ODBC approach there are ADO users and the techniques are shown as
> well.
>
> So we have the API way.. and their is ODBC way and ADO.NET providor as
> well.
>
> Lots of options ?
>
> Phil
> --
>
>
>


From: Phil McGuinness on 30 Mar 2006 18:35
Geoff,

snip[ ...and none of these help with a VO app using ADO right now <g>. ]

Read the previous few posts where using ADO they are connection to mySQL..

I repeat it here for you
========
Andrej,

first of all you have to specify into the ConnectString the OPTION=1 wich is
equivalent to the "Don't optimize column width" of the ODBC
Connector 3.51 (see Advanced tab / Flags 1 into your System DSN created for
MyDSQL ODBC entry).

some of the OPTION settings:
// Don't optimize column width = 1
// Return Matching Rows = 2
// Allow Big Results = 8
// Enable dynamic cursors = 32

A sample of Connection String is:

cConnectStatement:=Lower("Provider=MSDASQL;" + ;
"SERVER="+cGlobalSQLDataSource+";" + ;
"DSN="+cGlobalSQLNetworkLibrary+";" + ;
"DB="+cGlobalSQLInitialCatalog+";" + ;
"UID="+cGlobalUserName+";" + ;
"PWD="+cGlobalUserPass+";" + ;
"PORT=;OPTION=1;STMT=set names greek;")

oConn:Open(cConnectStatement ,NIL,NIL,NIL)

//adUseNone 1 Does not use cursor services. (obsolete)
//adUseServer 2 Default. Uses data-provider or driver-supplied cursors.
//adUseClient 3 Uses client-side cursors supplied by a local cursor
library.
oConn:CursorLocation:=adUseClient

AdoSetConnection(oConn)
AdoDateTimeAsDate(TRUE) // DD/MM/YYYY HH:MM:SS -> DD/MM/YY

My App uses VO2ADO to connect to both MS-SQL 2000/2005 via OLEDB and
MySQL
via ODBC Connector 3.51.

George Theopoulos
========

Phil McGuinness
-----------------

"Geoff Schaller" <geoffxxx(a)softwareobjectivesxxx.com.au> wrote in message
news:442c5b4a$1(a)dnews.tpgi.com.au...
> ...and none of these help with a VO app using ADO right now <g>.
>
> Thanks for the confirmation.


First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: MD5 encryption of a String
Next: RC.exe