Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / Ingres Topics / November 2005

Tip: Looking for answers? Try searching our database.

[Info-ingres] Visual Studio and Ingres .Net Providers

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Nigel Kavanagh - 30 Nov 2005 10:18 GMT
All,



I've added in the Ingres dot net providers as supplied in Ingres R3. We can
write code to connect to an Ingres database fine. But within Visual Studio
you can create data connections via wizards, it has a list of MS and Oracle
databases and others. Selecting others gives me a list of other .net
framework providers but not Ingres, even though all the dll's including VS
designer dll from CA are referenced in the project. What do we need to do to
enable the use of Ingres .Net providers via the toolbox/wizards?.





Regards

Nigel.

-------------------

Nigel J Kavanagh, Corporate Systems, Academic Services, Venn Building,
University of Hull, Cottingham Road, Hull.

HU6 7RX, England

Tel: 01482 466864, Fax: 01482 465930

N.J.Kavanagh@hull.ac.uk

Corporate Systems Support: corpsys@hull.ac.uk


thoda04 - 30 Nov 2005 17:55 GMT
Hi Nigel,

The Ingres r3 .NET Data Provider installation procedure usually installs the
Ingres connection, data adapter, and command components into the toolbox.
Dragging and dropping these components onto a design surface like a winform
launches the Ingres wizards.  If the installation process did not install
these components into the VS toolbox for some reason, there is a manual
procedure documented in the Ingres r3 Connectivity Guide, Chapter 12, near
page 12-45 to include them into the VS toolbox.

The Ingres .NET Data Provider is integrated with the VS toolbox, properties,
and solution windows, but not yet the Server Explorer.  The Server Explorer
was a closed interface in VS 2003.  It may be more open in VS 2005.  It's
something I'm looking at.

Hope this helps,
Dave


 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.