Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ TheIDE » U++ TheIDE: Compiling, Linking, Debugging of your packages » Cannot link SqlCommander sample with MSC8...  () 1 Vote
icon7.gif  Re: Cannot link SqlCommander sample with MSC8... [message #9194 is a reply to message #9145] Fri, 20 April 2007 16:56 Go to previous messageGo to previous message
Sbleck is currently offline  Sbleck
Messages: 16
Registered: April 2007
Location: Brazil
Promising Member

Hi Mirek,

Regarding to this issue...

Quote:


Look at the beginning of SqlCommander.cpp

#if defined(PLATFORM_WIN32) && defined(COMPILER_MSC)
#define HAVE_OLEDB
#endif

This means that OLEDB connections are disabled for migw, that is why it works...

You cannot compile it most likely because you have not installed part of SDK that provides OLEDB.

I suppose you are not very interested in OLEDB, therefore a simple way how to get around the problem is to disable for MSC too:

#if defined(PLATFORM_WIN32) && defined(COMPILER_MSC)
// #define HAVE_OLEDB
#endif



I've done as you suggested, but the problem remains:

----- SqlCtrl ( GUI NOAPPSQL MSC8 FORCE_SPEED WIN32 MSC ) (1 / 17)
----- Oracle ( GUI NOAPPSQL MSC8 FORCE_SPEED WIN32 MSC ) (2 / 17)
----- OleDB ( GUI NOAPPSQL MSC8 FORCE_SPEED WIN32 MSC ) (3 / 17)
OleDB.cpp
c:\upp\uppsrc\oledb\OleDB.h(14) : fatal error C1083: Cannot open include file: 'msdasc.h': No such file or directory
OleDB: 1 file(s) built in (0:01.45), 1453 msecs / file, duration = 1469 msecs

There were errors. (0:01.64)


But maybe could be useful to have OLEDB installed, because SqlCommand offered the possibility of this type of connection (to MS-Access files or SQL Server ?):

When connecting a database, DSN-less connections are superior to System DSN connections in performance. However, there will be no noticeable improvement in performance for smaller sites which have few concurrent connections only.

Although a DSN-less connection is operationally identical to a DSN but it doesn' t have to access registry during connecting process. For DSN-less connection, all required information will be specified in the connection string instead of storing in registry.

In practice, you?re recommended to use OLEDB connections over these two type of connections. Why? It?s because OLEDB can provide better performance in database connections and faster access to data.

The Connection String for OLEDB would be:

"Provider=ProviderName; Data Source=DatabaseSource; Initial Catalog=DatabaseName; User ID=UserID; Password=Password"


What are your recommendations, when performing another Windows SDK (WEB Install) installation ? What choice should be useful to add ?

Tks in adv,
Sven
 
Read Message icon5.gif
Read Message icon9.gif
Read Message
Read Message icon5.gif
Read Message icon7.gif
Read Message
Read Message icon7.gif
Read Message
Read Message icon12.gif
Read Message icon5.gif
Read Message
Read Message icon4.gif
Read Message
Read Message icon7.gif
Read Message
Read Message icon9.gif
Previous Topic: GCC 4.1.2 for Windows and Ultimate++
Next Topic: Attempting to compile U++ drawing examples
Goto Forum:
  


Current Time: Sun Jul 06 11:41:00 CEST 2025

Total time taken to generate the page: 0.03673 seconds