pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedVisual Basic/Data Environment Designer/PgODBC
5+ messages / 3 participants
[nested] [flat]
* Visual Basic/Data Environment Designer/PgODBC
@ 1999-11-10 04:00 bryan_napier@mindspring.com
0 siblings, 0 replies; 5+ messages in thread
From: bryan_napier@mindspring.com @ 1999-11-10 04:00 UTC (permalink / raw)
To: pgsql-interfaces
I have looked through the mailing list and was unable to find anything
that matched my exact problem/dilemna, or anything that offered any
solutions, so I apologize in advance if this has already been addressed
(I am new to the mailing list :-( )...
Anyhow, on with my problem..
I am using Visual Basic 6.0 Enterprise w/ SP3 on a Windows NT 4.0 SP4
machine... I have up till now been accessing databases resident on an
MS SQL 7 server...
Using the MS SQL 7 server I am able to go into the Visual Basic IDE,
enter the Data Environment Designer, and construct a simple Command with
the SQL Query Builder that constructs the following SQL query:
SELECT test_field FROM tbl_test WHERE (test_field=?)
And that will grab the necessary information about the test_field and
create a parameter for that command object... This works great with
MS SQL 7... However, when I do the same thing with Postgres, I get an
error message telling me "Unable to determine parameter information"...
Now, it still creates a parameter object for the command, it just
doesn't automatically detect the variable type, size, etc.... I can
still set the parameter options manually, set a value to the parameter ,
and run my query without error, it would just make life easier if
Postgres provided the VB DED with the information that it needs to
automatically detect this information..
Is this a bug in PgODBC, or is this one of Microsoft's many non-industry
standard protocol "enhancements" that allows it to do this?
Thanks in advance!
Bryan Napier
^ permalink raw reply [nested|flat] 5+ messages in thread
* Visual Basic/Data Environment Designer/PgODBC
@ 2000-02-21 23:26 Herbert Rabago Ambos <herbert@hindang.msuiit.edu.ph>
0 siblings, 0 replies; 5+ messages in thread
From: Herbert Rabago Ambos @ 2000-02-21 23:26 UTC (permalink / raw)
To: bryan_napier@mindspring.com; +Cc: pgsql-interfaces
Hi,
I have read your posting (dated 11-09-1999) about the Data Environment
using VB from the mail archives (see attached) and actually I have the
same problem too.
I VB programmer but kinda new to Data Environment (introduced on VB6) and
I am beginning to like it. It's really nice to see SQL construct,
command, etc on one object than flooding forms with Remote Data Control or
similar ADO's....
My problem is I have been having a problem of writting data to Postgres
using the Data Environment object. Viewing data from Postgres was easy
and no problem about that.
I pressumed that you've gone through this problem and thought you can help
me.
Thank you.
HERBERT
Attachments:
msg00057.txt (text/plain, 1.8K) download
From: bryan_napier@mindspring.com
To: pgsql-interfaces@postgresql.org
Subject: Visual Basic/Data Environment Designer/PgODBC
Date: Tue, 09 Nov 1999 23:00:45 -0500
--------------------------------------------------------------------------------
I have looked through the mailing list and was unable to find anything
that matched my exact problem/dilemna, or anything that offered any
solutions, so I apologize in advance if this has already been addressed
(I am new to the mailing list :-( )...
Anyhow, on with my problem..
I am using Visual Basic 6.0 Enterprise w/ SP3 on a Windows NT 4.0 SP4
machine... I have up till now been accessing databases resident on an
MS SQL 7 server...
Using the MS SQL 7 server I am able to go into the Visual Basic IDE,
enter the Data Environment Designer, and construct a simple Command with
the SQL Query Builder that constructs the following SQL query:
SELECT test_field FROM tbl_test WHERE (test_field=?)
And that will grab the necessary information about the test_field and
create a parameter for that command object... This works great with
MS SQL 7... However, when I do the same thing with Postgres, I get an
error message telling me "Unable to determine parameter information"...
Now, it still creates a parameter object for the command, it just
doesn't automatically detect the variable type, size, etc.... I can
still set the parameter options manually, set a value to the parameter ,
and run my query without error, it would just make life easier if
Postgres provided the VB DED with the information that it needs to
automatically detect this information..
Is this a bug in PgODBC, or is this one of Microsoft's many non-industry
standard protocol "enhancements" that allows it to do this?
Thanks in advance!
Bryan Napier
* Re: [INTERFACES] Visual Basic/Data Environment Designer/PgODBC
@ 2000-02-22 22:06 Herbert Rabago Ambos <herbert@hindang.msuiit.edu.ph>
0 siblings, 0 replies; 5+ messages in thread
From: Herbert Rabago Ambos @ 2000-02-22 22:06 UTC (permalink / raw)
To: Jason Doller <rjd@intekom.co.za>; +Cc: pgsql-interfaces
Jason,
Thank you for responding
>
> When you set up the ODBC datasource, did you check to make sure
> you hadn't createdit Read Only?
>
YES, and it was unchecked. I had viewed the log file and the following
substring appeared:
READONLY=1
Anyway here's some of the Data Environment Properties
Data Environment
Name=dePIS
Public=False
DECConnections
Name=ConnPostgres
ConnectionSource=Provider=MSDASQL.1;Persist Security
Info=False;Extended Properties="
PORT=5432;READONLY=1;PROTOCOL=6.4;
FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;
ROWVERSIONING=0;SHOWSYSTEMTABLES=0;
CONNSETTINGS="
CursorLocation=3adUseClient
DECCommands
Name=SQLEmployeeInfo
ConnectionName=ConnPostgres
CursorLocation=3adUseClient
CursorType=2adOpenDynamic
Hope you guys can help...
HERBERT
^ permalink raw reply [nested|flat] 5+ messages in thread
* RE: [INTERFACES] Visual Basic/Data Environment Designer/PgODBC
@ 2000-02-23 08:20 Dave Page <dpage@vale-housing.co.uk>
0 siblings, 0 replies; 5+ messages in thread
From: Dave Page @ 2000-02-23 08:20 UTC (permalink / raw)
To: pgsql-interfaces
> -----Original Message-----
> From: Herbert Rabago Ambos [mailto:herbert@hindang.msuiit.edu.ph]
> Sent: 22 February 2000 22:06
> To: Jason Doller
> Cc: pgsql-interfaces@postgreSQL.org
> Subject: Re: [INTERFACES] Visual Basic/Data Environment
> Designer/PgODBC
>
> >
> > When you set up the ODBC datasource, did you check to make sure
> > you hadn't createdit Read Only?
> >
>
> YES, and it was unchecked. I had viewed the log file and the
> following
> substring appeared:
>
> READONLY=1
READONLY=1 means that the datasource *is* read only. There are two settings
for this in the driver, one on the 'Advanced Options (Driver)'dialogue and
one on the 'Advanced Options (Datasource)' dialogue. Make sure both are
unchecked.
Regards,
Dave.
--
NASA uses Windows? Oh great. If Apollo 13 went off course today
the manual would just tell them to open the airlock, flush the astronauts
out, and re-install new ones! - Kibo in the SDM.
http://www.pgadmin.freeserve.co.uk (Home of pgAdmin)
^ permalink raw reply [nested|flat] 5+ messages in thread
* RE: [INTERFACES] Visual Basic/Data Environment Designer/PgODBC
@ 2000-02-23 10:11 Dave Page <dpage@vale-housing.co.uk>
0 siblings, 0 replies; 5+ messages in thread
From: Dave Page @ 2000-02-23 10:11 UTC (permalink / raw)
To: pgsql-interfaces
> -----Original Message-----
> From: Thomas Tang [mailto:tang@future.com.cn]
> Sent: 23 February 2000 08:51
> To: Dave Page
> Subject: RE: [INTERFACES] Visual Basic/Data Environment
> Designer/PgODBC
>
>
> I have the same problem. I've unchecked both two settings in the
> driver(datasource and advanced), but it still didn't work. I
> can even create
> a table, but I can not insert & update records in the table.
ADO (which I assume the Data Environment uses) will make an individual
recordset read only if you include a semi-colon at the end of the query (as
you would in psql), but won't issue an error as it (unlike DAO) assumes that
any query syntax is legal unless the remote db says otherwise. It does make
the recordset readonly though as it can't correctly parse the select to
figure out what insert/update query to issue.
This one got me when I first started using ADO as DAO though far more picky
about syntax, didn't mind the ';'.
Regards,
Dave.
--
NASA uses Windows? Oh great. If Apollo 13 went off course today
the manual would just tell them to open the airlock, flush the astronauts
out, and re-install new ones! - Kibo in the SDM.
http://www.pgadmin.freeserve.co.uk (Home of pgAdmin)
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2000-02-23 10:11 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-11-10 04:00 Visual Basic/Data Environment Designer/PgODBC bryan_napier@mindspring.com
2000-02-21 23:26 Visual Basic/Data Environment Designer/PgODBC Herbert Rabago Ambos <herbert@hindang.msuiit.edu.ph>
2000-02-22 22:06 Re: [INTERFACES] Visual Basic/Data Environment Designer/PgODBC Herbert Rabago Ambos <herbert@hindang.msuiit.edu.ph>
2000-02-23 08:20 RE: [INTERFACES] Visual Basic/Data Environment Designer/PgODBC Dave Page <dpage@vale-housing.co.uk>
2000-02-23 10:11 RE: [INTERFACES] Visual Basic/Data Environment Designer/PgODBC Dave Page <dpage@vale-housing.co.uk>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox