Connect to database

[mcosta]

First of all,

you shouldn't translate database connection parameters.

Second, why do you use QODBC driver and not QPSQL?

[seink]

just to be sure, when you say translate you mean de tr() that I use around my char[] s, right?
If I don`t translate it, it gives me an error saying that there is no function for char[], if I try to put it untranslated on a QString it gives me a "conversion from const char[] to QChar is ambiguous". I will try using it from a textfield but I don`t have much hope it will change anything.
Second, 'why' you ask? boss orders, of course! XD. But now following what you said, I tried with QPSQL and got a:

QSqlDatabase: QPSQL driver not loaded
QSqlDatabase: available drivers: QSQLITE, QODBC3, QODBC
"Driver not loaded Driver not loaded"

QSqlDatabase: QPSQL driver not loaded
QSqlDatabase: available drivers: QSQLITE, QODBC3, QODBC
"Driver not loaded Driver not loaded"

To copy to clipboard, switch view to plain text mode 

So I think I have better chances with anyone of those three....

[mcosta]

If you MUST use ODBC you have to configure ODBC on your system and provide the correct database name

void QSqlDatabase::setDatabaseName ( const QString & name )
....
For the QODBC driver, the name can either be a DSN, a DSN filename (in which case the file must have a .dsn extension), or a connection string.
For example, Microsoft Access users can use the following connection string to open an .mdb file directly, instead of having to create a DSN entry in the ODBC manager:
...
db = QSqlDatabase::addDatabase("QODBC");
db.setDatabaseName("DRIVER={Microsoft Access Driver (*.mdb)};FIL={MS Access};DBQ=myaccessfile.mdb");
if (db.open()) {
// success!
}
...
There is no default value.

To correct configure ODBC use documentation.

I suggest you to not use QObject::tr because if you translate your app, the connection parameters cannot be changed

[seink]

Following you advice I had a fist fight with my boss and, after braking my arm and foot, he decided that it would cost less to try compile qt to use the postgre pluging than to pay for my medical bill.
Now I`m trying to compile the qt adding the psql plugin.....

(of course I`m exagerating, but thats the feeling I have everytime he glares at me XD)

[mcosta]

You have to compile only the plugin not all Qt.

See here

Using native drivers can improve the performance, this is why Qt suggest to use ODBC as "LAST" solution if native drivers cannot be used.

[seink]

I`m getting and odd error....
Warning!: I`m a windows user so I`m not familiar with compiling and such in cmd prompt =p
The error I`m getting is 'Permission Denied' when I do nmake, but I`m using the admin acc to pass the commands....

C:\Qt\4.7.2\src\plugins\sqldrivers\psql>nmake
 
Microsoft (R) Program Maintenance Utility Version 10.00.30319.01
Copyright (C) Microsoft Corporation.  All rights reserved.
 
        "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\nmake.exe" -
f Makefile.Debug
 
Microsoft (R) Program Maintenance Utility Version 10.00.30319.01
Copyright (C) Microsoft Corporation.  All rights reserved.
 
        g++ -c -g -frtti -fexceptions -mthreads -Wall -DUNICODE -DQT_LARGEFILE_S
UPPORT -DQT_NO_CAST_TO_ASCII -DQT_NO_CAST_FROM_ASCII -DQT_DLL -DQT_PLUGIN -DQT_S
QL_LIB -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_3DNOW -DQT_HAVE_SSE -DQT_HAVE_MMXEX
T -DQT_HAVE_SSE2 -DQT_THREAD_SUPPORT -I'../../../../include/QtCore' -I'../../../
../include/QtSql' -I'../../../../include' -I'c:/Program' -I'Files/PostgreSQL/9.0
/include' -I'../../../../include/ActiveQt' -I'debug' -I'../../../../mkspecs/win3
2-g++' -o debug/main.o main.cpp
NMAKE : fatal error U1045: spawn failed : Permission denied
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 10.0
\VC\bin\nmake.exe"' : return code '0x2'
Stop.
 
C:\Qt\4.7.2\src\plugins\sqldrivers\psql>

C:\Qt\4.7.2\src\plugins\sqldrivers\psql>nmake

Microsoft (R) Program Maintenance Utility Version 10.00.30319.01
Copyright (C) Microsoft Corporation.  All rights reserved.

        "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\nmake.exe" -
f Makefile.Debug

Microsoft (R) Program Maintenance Utility Version 10.00.30319.01
Copyright (C) Microsoft Corporation.  All rights reserved.

        g++ -c -g -frtti -fexceptions -mthreads -Wall -DUNICODE -DQT_LARGEFILE_S
UPPORT -DQT_NO_CAST_TO_ASCII -DQT_NO_CAST_FROM_ASCII -DQT_DLL -DQT_PLUGIN -DQT_S
QL_LIB -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_3DNOW -DQT_HAVE_SSE -DQT_HAVE_MMXEX
T -DQT_HAVE_SSE2 -DQT_THREAD_SUPPORT -I'../../../../include/QtCore' -I'../../../
../include/QtSql' -I'../../../../include' -I'c:/Program' -I'Files/PostgreSQL/9.0
/include' -I'../../../../include/ActiveQt' -I'debug' -I'../../../../mkspecs/win3
2-g++' -o debug/main.o main.cpp
NMAKE : fatal error U1045: spawn failed : Permission denied
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 10.0
\VC\bin\nmake.exe"' : return code '0x2'
Stop.

C:\Qt\4.7.2\src\plugins\sqldrivers\psql>

To copy to clipboard, switch view to plain text mode 

[szisziszilvi]

Are you sure you have nmake? I have also builded qpsgl recently and the solution was to use mingw32-make instead. True, the symptom was very different, but still, if works, then fine. Was the previous step (the one with qmake) succesful?

[mcosta]

I see

../include/QtSql' -I'../../../../include' -I'c:/Program' -I'Files/PostgreSQL/9.0
/include' -I'../../../../include/ActiveQt' -I'debug' -I'../../../../mkspecs/win3
2-g++' -o debug/main.o main.cpp

Notice that the path "C:/Program Files" was splitted
Try Quoting using qmake like

qmake "INCLUDEPATH+="\"C:\Program Files\PostgreSQL\9.0\include\"" "LIBS+=\"C:\Program Files\PostgreSQL\9.0\"\lib\ms\libpq.lib" psql.pro

qmake "INCLUDEPATH+="\"C:\Program Files\PostgreSQL\9.0\include\"" "LIBS+=\"C:\Program Files\PostgreSQL\9.0\"\lib\ms\libpq.lib" psql.pro

To copy to clipboard, switch view to plain text mode