ODBC connection in current 4D process

[Tetu, Norm]

I'm upgrading an application that uses an external data source to 4D
2004.  I was able to get everything working using ODBC Pro, but because
of the license cost I'm rewriting the code to use the built-in 2004 ODBC
commands.

My ODBC LOGIN works and successfully connects to the database, and I can
query the database within that process.  If I issue the ODBC EXECUTE
command from a different process ID, I get a "no open connection" error.
I understand that the connection is good for that process, but the ODBC
LOGIN is done in a Global Process, so I thought I would be able to use
that connection from another Global Process.

If this isn't possible, is there another way to access the database
throughout the application without having multiple simultaneous
connections?  That process is relatively simple with ODBC Pro since that
plug-in maintains a ConnectionID and StatementID that can be used for
subsequent access.

Thanks, Norm


**********************************************************************
4D Basics hosted by 4D, Inc.                       http://www.4D.com/

Register for 4D Summit 2009 Today
Early Bird Pricing Ends August 28th - http://www.4D.com/summit

To Unsubscribe:                        mailto:4DBasics-off@...
**********************************************************************

[Mehboob Alam]

Norm,

This is a beginners list - you may want to post your query again in the regular NUG list.
The signup form is on the 4D.com website.

 sincerely,
mehboob alam




Electricity is actually made up of extremely tiny particles called electrons,
that you cannot see with the naked eye unless you have been drinking.
- Dave Barry



----- Original Message ----
From: "Tetu, Norm" <Norm.Tetu@...>
To: 4DBasics@...
Sent: Wednesday, July 29, 2009 6:51:23 AM
Subject: ODBC connection in current 4D process

I'm upgrading an application that uses an external data source to 4D
2004.  I was able to get everything working using ODBC Pro, but because
of the license cost I'm rewriting the code to use the built-in 2004 ODBC
commands.

My ODBC LOGIN works and successfully connects to the database, and I can
query the database within that process.  If I issue the ODBC EXECUTE
command from a different process ID, I get a "no open connection" error.
I understand that the connection is good for that process, but the ODBC
LOGIN is done in a Global Process, so I thought I would be able to use
that connection from another Global Process.

If this isn't possible, is there another way to access the database
throughout the application without having multiple simultaneous
connections?  That process is relatively simple with ODBC Pro since that
plug-in maintains a ConnectionID and StatementID that can be used for
subsequent access.

Thanks, Norm


**********************************************************************
4D Basics hosted by 4D, Inc.                      http://www.4D.com/

Register for 4D Summit 2009 Today
Early Bird Pricing Ends August 28th - http://www.4D.com/summit

To Unsubscribe:                        mailto:4DBasics-off@...
**********************************************************************


     

**********************************************************************
4D Basics hosted by 4D, Inc.                       http://www.4D.com/

Register for 4D Summit 2009 Today
Early Bird Pricing Ends August 28th - http://www.4D.com/summit

To Unsubscribe:                        mailto:4DBasics-off@...
**********************************************************************