OdbcConnection DBConn = null;
DataSet DSPageData = new DataSet();
string dbpath = @"\\servername\directoryname";
DBConn = new OdbcConnection("Driver={Microsoft Access Driver (*.mdb)};Dbq=" + dbpath + "databasename.mdb;UID=;PWD=;");

Connection String for pyodbc, using a system DSN

"DSN=dsn_name;UID=username;PWD=passwd"

Connection String for sqlalchemy, using a system DSN

'mssql://username:passwd@/?dsn=dsn_name'

Leave the @ symbol after the passwd and don't use an @ symbol in your passwd (guilty). I assume the symbol is used in the parsing of the string, why I am not so sure on.

saat gua konfigurasi ODBC di vista, gua kagak bisa konek ke server. server database gua pakai 2003 server. gua bingung tuh... masak aplikasi gua kagak bisa jalan... akhirnya gua nanya lah ke IT clien gua, ada yang pernah konfigurasi ODBC di clien. e... malah mereka bilang maaf mas, vista memang masih belum stabil, dilihatin tuh artikel tentang vista yang belum support ODBC, gua tambah stress pada saat itu.. didepan bos besar clien masak gua kagak bisa nginstall aplikasi gua... he..he...

alhasil setelah 1,5jam gua otak-atik tu vista, dapat hasil juga gua. aplikasi gua bisa jalan tuh di vista, tapi laporannya ga bisa tampil soalnya konfigurasi ODBCnya gagal dibuat. aplikasi gua pakai 2 macam koneksi : tembak server langsung [aplikasi] & DSN [repot/crystall repot], nah yang tembak lansung ke server bisa... akhirnya gua putus asa, gua bikin tuh DSN [ODBC] dengan nama yang sesuai dengan yang diminta ama repot gua, walaupun DSN ga bisa konek ke server gua tetep bikin tu DSN.

puji syukur sih, saat gua coba jalanin system dan nyoba repotnya muncul tuh repot, bener lagi. ya akhirnya dari pengalaman yang gua alami itu, gua narik kesimpulan bahwa crystall repot itu mampu buat koneksi sendiri yang penting dikasih jalannya aja... he..he... [moga ga untung-untungan tu koneksi ODBC]

ya intinya kalo rekan-rekan mau koneksi ke server pakai ODBC, seandainya kejadiannya kayak gua, ya rekan-rekan paksain aja itu nama DSN [ODBC]nya biar nanti CRnya yang create koneksinya sediri,, yang penting kalian kasih alamatnya nanti si CR yang cari kunci ama buka pintunya... he.. he...

semoga bermanfaat....

ant

Finalmente, la conexión la he realizado a través de ODBC.

Para generar una conexión desde ODBC:

Inicio -> Configuración -> Panel de control -> Herramientas administrativas -> Orígenes de datos (ODBC).

Se puede crear un DSN de usuario o de sistema, dependiendo de la visibilidad que se quiera dar.

Se pulsa sobre el botón "Agregar". En la pantalla se selecciona el driver para SQL Server.

Se configuran los datos que el asistente va pidiendo. El dato importante es qué base de datos se desea especificar como predeterminada, ya que por defecto se conectará a esta base de datos.

En el código, se crea la conexión de la siguiente forma:
Connection con =
DriverManager.getConnection("jdbc:odbc:NombreConexión", "usuario", "contraseña");

I made this script to verify our inventory of computers.
It's a nice and simple example of ODBC use in vbscript.
This is part of a larger "all-in-one" loginscript.
You'll need an Access 2000 DB with 1 table: "devices" with
all corresponding fields in the script (bottom section).
NO error-handling yet!

'******************************************
' Device information to Access DB on login.
'******************************************
' Use, modify or share it but don't hold me
' responsible.
' Created by Stanny Nuytkens -2008-
' http://dhalicious.wordpress.com
' This is part of a all-in-one loginscript
' that I'm currently working on.
'*****************************************' connectionstring, connection, recordset, network object 

Dim cs, cn, rs, net
' values to get:
Dim id, user, osname, osversion, osmanufacturer, osconfiguration, osbuildtype, owner, organization, _
pid, installdate, uptime, windir, sysdir, bootdevice, locale, timezone, totphysmem, avphysmem, _
totpagefile, avpagefile, sysmanufacturer, sysmodel, systype, domain, cpus, biosversion, officeversion

strComputer = "."   ' local PC
' connection string for access 2000 DB file (mdb)
cs = "Driver={Microsoft Access Driver (*.mdb)};Dbq=use.mdb;Uid=Admin;Pwd=;"
' create word instance to check office version
set wrdapp = createobject("Word.Application")

set dicProductType = CreateObject("Scripting.Dictionary")
dicProductType.Add 1, "Workstation"
dicProductType.Add 2, "Domain Controller"
dicProductType.Add 3, "Standalone Server"
set objWMIDateTime = CreateObject("WbemScripting.SWbemDateTime")
set objWMI = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")
set colOS = objWMI.InstancesOf("Win32_OperatingSystem")
set colCS = objWMI.InstancesOf("Win32_ComputerSystem")
set colBIOS = objWMI.InstancesOf("Win32_BIOS")
Set cn = CreateObject("ADODB.Connection")
Set rs = CreateObject("ADODB.Recordset")
Set net = CreateObject("WScript.NetWork")

' collect values and put them in variables
for each objOS in colOS
   id = objOS.CSName
   osname = objOS.Caption
   osversion = objOS.Version & "_" & objOS.BuildNumber
   osmanufacturer = objOS.Manufacturer
   osconfiguration = dicProductType.Item(objOS.ProductType)
   osbuildtype = objOS.BuildType
   owner = objOS.RegisteredUser
   organization = objOS.Organization
   pid = objOS.SerialNumber
   objWMIDateTime.Value = objOS.InstallDate
   installdate = objWMIDateTime.GetVarDate
   objWMIDateTime.Value = objOS.LastBootUpTime
   uptime = objWMIDateTime.GetVarDate
   windir = objOS.WindowsDirectory
   sysdir = objOS.SystemDirectory
   bootdevice = objOS.BootDevice
   locale = objOS.Locale
   timezone = "GMT" & objOS.CurrentTimezone
   totphysmem = round(objOS.TotalVisibleMemorySize / 1024) & " MB"
   avphysmem = round(objOS.FreePhysicalMemory / 1024) & " MB"
   totpagefile = round(objOS.TotalVirtualMemorySize / 1024) & " MB"
   avpagefile = round(objOS.FreeVirtualMemory / 1024) & " MB"
next
for each objCS in colCS
   sysmanufacturer = objCS.Manufacturer
   sysmodel = objCS.Model
   systype = objCS.SystemType
   domain = objCS.Domain
   cpus = objCS.NumberofProcessors
next
intCount = 0
for each objBIOS in colBIOS
   biosversion = objBIOS.Version
next

' extra values, office version and username
officeversion = mid(wrdapp.build,1,2)
user = net.UserName

cn.Open cs

' create recordset
rs.Open "SELECT * FROM device WHERE ID='" & id & "'",cn,3,3

' check if entry ID (PC name) allready exists in DB
if rs.EOF then
rs.AddNew
DB_fill()
rs.Update
' new entry added
wscript.echo "New PC added to DB..."
Else
DB_fill()
rs.Update
' existing entry updated
wscript.echo "DB update!"
end if

' close connection
rs.close
cn.close

' cleanup
wrdapp.quit
set wrdapp = Nothing
set dicProductType = Nothing
set objWMIDateTime = Nothing
set objWMI = Nothing
set colOS = Nothing
set colCS = Nothing
set colBIOS = Nothing
Set cn = Nothing
Set rs = Nothing
Set net = Nothing

'--------------------Sub that Fills DB with values (used in IF structure)
'--------------------Access DB (2000), 1 table with these fields is used to store.
Sub DB_fill()
   rs("ID") = id
   rs("USER") = user
   rs("OSNAME") = osname
   rs("OSVERSION") = osversion
   rs("OSMANUFACTURER") = osmanufacturer
   rs("OSCONFIGURATION") = osconfiguration
   rs("OSBUILDTYPE") = osbuildtype
   rs("OWNER") = owner
   rs("ORGANIZATION") = organization
   rs("PID") = pid
   rs("INSTALLDATE") = installdate
   rs("UPTIME") = uptime
   rs("WINDIR") = windir
   rs("SYSDIR") = sysdir
   rs("BOOTDEVICE") = bootDevice
   rs("LOCALE") = locale
   rs("TIMEZONE") = timezone
   rs("TOTPHYSMEM") = totphysmem
   rs("AVPHYSMEM") = avphysmem
   rs("TOTPAGEFILE") = totpagefile
   rs("AVPAGEFILE") = avpagefile
   rs("SYSMANUFACTURER") = sysmanufacturer
   rs("SYSMODEL") = sysmodel
   rs("SYSTYPE") = systype
   rs("DOMAIN") = domain
   rs("CPUS") = cpus
   rs("BIOSVERSION") = biosversion
   rs("OFFICEVERSION") = officeversion
End sub

So I received a rather nice communication from Mario G. of GotMVC.Com who has apparently gotten WordPress v2.5.1 to work on his Windows Deluxe hosting account. After viewing his PHPInfo results he is running PHP version 5.2.5 on Windows IIS7. As far as I know, no existing account has the IIS7 option, so only new accounts have this option, but this is a pretty good sign that GoDaddy is finally moving in the right direction with their servers and software support.

Additionally, the GoDaddy Hosting blog posted this on the 16th of June further proving their support of PHP5 and IIS 7 but only on newly opened accounts. Sounds like all of us PHP 4, IIS 6 users need to get on the phone with GoDaddy. I know I will.

Original Post:

So time and time again I see people wanting to adapt the famous Wordpress blogging system to their GoDaddy hosting account, with no success. Now, if you happen to have the Linux hosting package, then you are probably thinking, 'what are you talking about?'. Well for those of you who do happen to have their sites cozied up with the Linux package, then aside from a lack of support for certain features such as post-by-email you don't have much to worry about. There are however hundreds, if not thousands, of people who have Windows hosting packages for various reasons such as the utilization of the .Net framework. For those of us who do rely on the Windows hosting, there is no support for PHP anymore, yet as you will find PHP pages will still run to a limited extent.

What I have come to find through my extensive research is that there is still some form of PHP support available on most every Windows server in GoDaddy's extensive nature from what appears to be left behind from previous offerings and attempts. There are however many restrictions in place that restrict Wordpress from running correctly without extreme modification to the source files. I was able to run a PHP page which output the of so wonderful 'phpinfo()' function. Just to give you an idea of what we are working with here is a list of the disabled functions. Bear with me, it is pretty long:

getmyinode, getopt, getrusage, extension_loaded, dl, mysql_pconnect, crack_check, crack_closedict, crack_getlastmessage, crack_opendict, fsockopen, pfsockopen, mysql_list_dbs, mysql_stat, ini_get, ini_get_all, ini_alter, ini_set, get_current_user, get_defined_constants, get_include_path, php_ini_scanned_files, php_uname, phpcredits, restore_include_path, set_include_path, set_time_limit, version_compare, zend_version, getmypid, getmyuid, getmygid, assert_options, assert, fopen, fwrite, fread, file, fpassthru, file, mail, opendir, readdir, closedir

Now, what you will find here is that a majority of the functions required to go through the Wordpress installation routine, or even access your Wordpress blog are disabled. Without 'fopen()' or 'fwrite()' Wordpress is unable to create your custom 'wp-config.php' file. Without 'ini_get()' or 'ini_set()' Wordpress is again unable to continue on past many of the functions. The biggest problem however that I am sure many of you are more than familiar with is the error that results when you try to connect to your MySQL database.

The problem here is that the version of PHP in place on these servers (in most cases 4.3.11) requires an updated connector to interface with MySQL 4.0 and especially MySQL 5.0 databases. The work-around here would be to convert the entire Wordpress system to use the ODBC connector version 3.5.1. I have had success getting Wordpress to connect to the database after modifying it to use the ODBC connector however you will find that Wordpress will never populate your database with the schema it needs. This is because the 'schema.php' file which stores the SQL to create the database cannot execute properly without all of the variables and environment information discovered in the other files that handle the Wordpress installation process.

Because of this problem, unless the entire system is converted to work around all of the disabled functions and MySQL connector reliance you would have an easier time converting your entire site to PHP and using a Linux server than converting the entire Wordpress installation to a GoDaddy Windows server friendly software set. Hopefully this post will serve to save some other the frustration and anger that can easily come about when you see a PHP page work on your Windows server but can't ever seem to get Wordpress actually running.

Thank you,

Geoff Kauten
www.KautenEffects.com

I must import a MS Access database to a SQL Server Database

At the first time, I thinked the follows idea:

• From Access: Export Data -> Not Work
• From ODBC: Create an ODBC driver and try to connect with it -> Not Work

Other idea? Oh yes ... I think to use the ADP. What do you do? Read it step by step:

1. On SQL Server create a new database (data destination)
2. On MS Access: File -> New -> "project using existing data..." and select the server (SQL) and the database destination (it was created on step 1)
3. On MS Access: Import the table from the mdb file (source database) and you can do it with: File -> Load External Data* -> Import
4. Select all table (or only the table you need)
5. Please wait ...
6. When the process end, you can have the data on your SQL Server Database

Is it not difficult ;)

* I'm not sure of the name of this menu ... It's the 3th row under file.

Vamos usar um Banco de Dados Acess com ODBC para conectar com o Java. Tentarei mostrar da forma mais simples possível.

Primeiramente, crie um banco de dados no Access e salve em alguma pasta FIXA do seu projeto (um exemplo, crie uma pasta bf na pasta raiz do seu projeto).

Agora abra o Painel de Controle do Windows, vá em Ferramentas Administrativas -> Fonte de Dados (ODBC). Você pode selecionar a aba Fontes de Dados do Sistema, e então clique em Adicionar. Selecione Driver do Microsoft Access (*.mdb) e clique em Concluir, agora coloque um nome para o Alias do seu banco (esse alias serve para interligar o Java ao Banco), clique em Selecionar e escolha o caminho do banco. Pronto, agora pressione OK e pronto! Vamos então para a melhor parte: Programação! =]

Na sua classe, importe:
[sourcecode language='java']import java.sql.*;[/sourcecode]
Ela é que contém as classes necessárias para se conectar e manipular o banco.

Agora, dentro da classe, você pode definir uns objetos, um Connection, que manipula a conexão em si, e um Statement, que manipula o banco com querys. Assim:
[sourcecode language='java']public Connection con;
public Statement stm;[/sourcecode]
Agora, para facilitar, crie um método chamado Connectar:
[sourcecode language='java']public void Conectar()
{
//JOptionPane.showMessageDialog(null, "Preparando para iniciar a conexão com o BD;");

try
{
/* Tenta se conectar ao Driver */
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
}
catch (ClassNotFoundException e)
{
JOptionPane.showMessageDialog(null, "Impossível carregar o Driver.");
System.exit(0);
}
try
{
/* nomedobanco é o nome que você deu anteriormente ao seu alias */
con = DriverManager.getConnection("jdbc:odbc:nomedobanco");
stm = con.createStatement();
}
catch (SQLException sqle)
{
JOptionPane.showMessageDialog(null, "Problema ao conectar!");
System.exit(0);
}

//JOptionPane.showMessageDialog(null, "Conectado com sucesso!");
}[/sourcecode]
Você pode descomentar as linhas que mostram uma mensagem antes de se conectar e depois, só para ver como que é! ^^

Crie também uma função para desconectar, e se possível, chame-a antes de sair do seu programa:
[sourcecode language='java']public void Desconectar()
{
try
{
con.close();
}
catch (SQLException sqle)
{
JOptionPane.showMessageDialog(null, "Problema ao desconectar!");
System.exit(0);
}
}[/sourcecode]

Basicamente, agora você já pode se conectar e desconectar ao banco de dados! Excelente não?

Tá, imagino agora que você se perguntou: "Mas como vou manipulá-lo agora?"! Hmm, Boa pergunta!

Para manipular o Banco de Dados em si, como fazer consultas, inserções, remoções, é necessário a utilização de SQL, portanto se você não sabe, é melhor estudar um pouco! hehehe

Então, voltando para o Java...

Lembra-se do objeto Statement que criamos? Então, ele é o ponto chave agora! Para executar uma query, você usa o método execute dele, assim:
[sourcecode language='java']stm.execute("INSERT INTO tabela(nome, idade) VALUES('Bruno', 17)");[/sourcecode]
Porém ele NÃO traz retorno algum, ou seja, se você quiser fazer uma consulta, por exemplo, tem que usar o método executeQuery, que retorna um objeto ResultSet, que contém todo o resgistro retornado do banco de dados, a partir da consulta.
[sourcecode language='java']try
{
ResultSet rs = stm.executeQuery("SELECT * FROM tabela");
while (rs.next())
{
JOptionPane.showMessageDialog(null, "Nome: " + rs.getString("nome") + " - Idade: " + rs.getInt("idade"));
}
}
catch (SQLException e)
{
JOptionPane.showMessageDialog(null,"" + e.getMessage(),"Erro",0);
}
finally
{
rs.close();
}[/sourcecode]
O Objeto ResultSet, tem um método para pegar cada tipo do banco de dados. Dentro dele vai o parâmetro que é o nome do campo a ser pego!

Fácil? Não exatamente! Isso é muito básico, não inútil, mas básico. Portanto, você concerteza vai precisar de mais material, então acesse este magnífico site que você vai achar de tudo lá! =D

(Muito Obrigado ao ViniGodoy pela ajuda aqui! =D)

Valeu, até a próximaaa!

Esistono tantissime tipologie di database, ciascuna con una precisa peculiarità: MySQL, Oracle, MS SQL, Informix, Firebird, DB2, MDB Access e tanti altri. Per uniformare gli accessi ai vari database nel 1989 il SQL Access Group (SAG), di cui facevano parte i maggiori produttori di database, ha sviluppato un'interfaccia aperta e universale chiamata Open Database Connectivity (ODBC).

Tutti gli strumenti in grado di connettersi a fonti dati ODBC, un esempio fra tutti OpenOffice, potranno accedere ai dati contenuti nei database, semplicemente disponendo del relativo driver ODBC installato.

L'implementazione di ODBC più utilizzata su ambienti Linux è unixodbc ed è quella di cui faremo uso per osservarne il funzionamento e la configurazione. Prima di iniziare è necessario installare il pacchetto unixodbc con apt-get install unixodbc e un driver ODBC per il database a cui desideriamo connetterci. Utilizzando il pacchetto IBM iSeriesAccess visto in precedenza scopriamo come configurare il driver ODBC fornito nel pacchetto per connetterci ad un sistema iSeries ed una fonte dati denominata anche Data Source Name (DSN) che utilizzeranno i programmi per accedere al database scelto.

Configurare driver e DSN manualmente

La configurazione del driver ODBC può essere effettuata manualmente richiamando le impostazioni fornite dal pacchetto iSeriesAccess. All'interno di una finestra terminale eseguire:

sudo odbcinst -i -d -f /opt/ibm/iSeriesAccess/unixodbcregistration

L'avvenuta installazione verrà confermata da:

odbcinst: Driver installed. Usage count increased to 1.
Target directory is /etc

Terminata la configurazione del driver passiamo alla creazione di una fonte dati DSN. Possiamo configurarla sia di sistema, disponibile a tutti gli utenti, sia per singolo utente. Nel caso volessimo aggiungere un DSN di sistema modificheremo il file /etc/odbc.ini, mentre nel caso del singolo utente possiamo modificare il file .odbc.ini nella home dell'utente. Inseriremo al suo interno:

[iSeries]
Description             = Database iSeries Azienda
Driver                  = iSeries Access ODBC Driver
System                  = iseries.azienda
UserID                  = NOMEUTENTE
Password                = PAROLA D'ORDINE
Naming                  = 0
DefaultLibraries        = MIALIBRERIA
Database                =
ConnectionType          = 1
BlockFetch              = 1
BlockSizeKB             = 512

Il nome [iSeries] sarà il nome del DSN e verrà utilizzato dagli altri programmi per riferirsi a questa connessione, il campo Description è libero per l'inserimento di una descrizione qualsiasi, System identifica l'indirizzo del server a cui connettersi, qui ho utilizzato iseries.azienda. I campi UserID e Password identificano l'utente e la password per l'accesso al sistema, generalmente se un programma non ne fornisce di propri utilizza quelli qui definiti, se vengono lasciati in bianco, sarà onere dell'applicazione (OpenOffice o altro) di fornirne di validi.

Naming consente di definire il modello di separazione tra libreria e file: il valore 0 identifica la separazione SQL fatta con LIBRERIA.NOMEFILE, mentre il valore 1 identifica la separazione di sistema fatta con LIBRERIA/NOMEFILE. DefaultLibraries identifica l'elenco delle librerie predefinite separate da spazi dentro le quali ricercare i files/tabelle. Database indica il nome del database SQL da aprire.

Il valore ConnectionType consente di definire le tipologie di istruzioni eseguibili: il valore 0 consente tutte le operazioni, sia in lettura che scrittura che esecuzione; il valore 1 consente solamente le operazioni di lettura ed esecuzione mentre il valore 2 consente solo operazioni di lettura dei dati.

Gli ultimi due argomenti BlockFetch e BlockSizeKB consentono di definire la dimensione dei pacchetti che vengono richiesti al server per ogni singola operazione. Per ulteriori informazioni sui parametri utilizzati nella configurazione fare riferimento alla pagina Connection string keywords sul sito IBM.

Configurare driver e DSN con ODBCConfig

La configurazione del driver e del DSN è anche possibile utilizzando l'interfaccia grafica ODBCConfig che tuttavia richiede le librerie QT3 per un totale di circa 10 MB di pacchetti da scaricare. Per utilizzare ODBCConfig basterà installare il pacchetto unixodbc-bin e le sue librerie eseguendo sudo apt-get install unixodbc-bin in una finestra di terminale.

Purtroppo non viene inserito alcun collegamento tra i menu per cui può essere necessario inserirlo nel menu Applicazioni manualmente.

Per l'installazione del driver ODBC è necessario avviarlo con permessi amministrativi, per cui premiamo ALT+F2 ed eseguiamo gksudo ODBCConfig.

L'interfaccia si presenta a schede e le prime tre serviranno a definire i DSN, lasciamole stare per il momento, dobbiamo installare il driver ODBC prima. Spostiamoci quindi sulla quarta scheda Drivers, ovviamente vuota e clicchiamo il pulsante Add per aggiungerne uno nuovo.

Verranno richiesti il nome del driver ODBC, utilizzare quello fornito da IBM ovvero iSeries Access ODBC Driver e nei campi Driver, Driver64, Setup e Setup64 inserire le librerie che si trovano nelle cartelle lib e lib64 dove è stato installato l'iSeriesAccess. In generale vanno bene i dati mostrati nella figura sopra. Confermare i dati inseriti col primo pulsante a spunta in alto a sinistra.

Passiamo adesso alla configurazione del DSN, ricordando che per inserire un DSN di sistema è necessario avere privilegi amministrativi e se è stato avviato il programma mediante sudo i DSN dell'utente saranno dell'utente root e non dell'utente che esegue il comando. Per cui:

• Avvviare il programma con sudo se si desidera configurare i drivers ODBC o aggiungere DSN di sistema, su file per tutti gli utenti oppure solo per l'utente root
• Avviare il programma senza sudo se si desidera configurare i DSN per il proprio utente

Le tre schede dell'applicazione serviranno per assegnare rispettivamente DSN Utente, Sistema (per tutti gli utenti) e su File (per tutti gli utenti con accesso ai singoli files). La procedura tuttavia è uguale per tutti i tipi di DSN: cliccando Add sarà avviata la procedura guidata.

Verrà richiesto il driver ODBC da utilizzare: scegliere il driver iSeries Access ODBC Driver e premere OK per proseguire. I pulsanti Add, Remove e Configure si riferiscono ai driver, consentono di aggiungere, rimuovere e configurare un driver ODBC.

Immettere il nome del DSN (qui iSeries) e un'eventuale descrizione. Sul campo System immettere l'indirizzo del sistema a cui connettersi, qui abbiamo utilizzato iseries.azienda. Su UserID e Password è possibile indicare la coppia utente e password per l'accesso al server, lasciandole in bianco sarà onere dell'applicazione fornire i dati di accesso. Su DefaultLibraries è possibile inserire un elenco di librerie predefinite, in cui ricercare i dati, separate da spazi.

Per tutti gli altri campi è possibile cliccare sopra la terza icona in alto e poi sopra il campo di cui si desidera ricevere maggiori informazioni. Fare riferimento anche alla sezione della configurazione manuale per una breve spiegazione dei singoli valori oppure alla pagina Connection string keywords sul sito IBM. Il primo pulsante con la spunta in alto a sinistra servirà per confermare i dati scelti.

Giacomo Antolini ha scritto un'ottima guida alla configurazione del driver ODBC di iSeriesAccess da cui questa prende spunto.

Ulteriori informazioni sull'uso di unixodbc e sulla configurazione di altri driver ODBC possono trovarsi alla relativa pagina della documentazione sul sito unixodbc.

In drie stappen wordt de draaitabel gemaakt. Hier is gekozen om te werken met gegevens uit Excel, er kan ook gekozen worden om Een externe gegevensbron te gebruiken (ODBC).

Bij het kiezen van ODBC wordt hier gevraagd de juiste ODBC-koppeling aan te geven. In het scherm is te zien dat de gegevens opgehaald worden.

In de laatste stap kun je aangeven waar de gegevens worden geplaatst in Excel.

Klik op indeling om de gegevens in de gewenste vorm weer te geven. Sleep de gewenste gegevens naar het doel, de kolom of de recordkant. Er moet minimaal 1 veld naar gegevens worden gesleept.

Als de gegevens in Excel zijn weergegegven, zijn ze altijd te bewerken door gebruik van de werkbalk Draaitabel.

Sleep hiervoor de woorden die in de werkbalk staan naar de draaitabel toe. Of sleep ze uit de tabel terug naar de werkbalk om ze te verwijderen. Ook kun je items van de kolomkop naar de records slepen en andersom.

Van de draaitabel kan je met het knopje draaitabel in de werkbalk heel makkelijk een draaigrafiek maken.

note: I creating my search to a simple form

Steps in searching through out the database
1. First we had to define variables
2. Searxh field
3. A database connection
4. The search and opening the data
5. Display the outputed search

Firstly to process my example, I want show that there is a form, so what i wanna do is to create a form.Below are the exmple code of the form

<table>
<tr>
<form method="POST" action="search_results.asp">
<td>Search: <input type="text" name="txtSearch" size="50"></td>
</tr>
<tr>
<td><input type="submit" value="Search"></td>
</tr>
</table>

Then we could proceed to the search

1. Define variables

<%
Dim strInputSearch 'Variable for the search word
Dim strCon 'connect to the database
Dim adoCon 'Database Connection Variable Object
Dim strSQL 'SQL query for the database
Dim rsSearch 'search recordset storage
2. Search field

This would be variable that has the search word

strInputSearch = Request.Form("txtSearch")

This makes it so people cant inject SQL code and/or cause some unwanted errors

strInputSearch = Replace(strInputSearch,"'", "''", 1, -1, 1)

3. Database Connection

This is setting-up the connection

Set adoCon = Server.CreateObject("ADODB.Connection")

This is that hold the connection string

strCon = "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" &Server.MapPath("database.mdb")

Open the connection for the database

adoCon.Open strCon

4. Opening the search from the database

Set the database connection

Set rsSearch = Server.CreateObject("ADODB.Recordset")

This is the SQL statement for searching.

strSQL = "SELECT tblTable.* FROM tblTable WHERE tblTable.Field LIKE '%" & strInputSearch & "%';"

Opens the database so we can get the results of the search

rsSearch.Open strSQL, adoCon

5. And then we had to display our search by means of this

If there are no matches then continue

If rsSearch.EOF Then

'Write out the message that there are no matches
Response.Write("There are no matches with your search")

'If there are matches, continue
Else

'Loop through the database to display all the matches
DO UNTIL rsSearch.EOF

'Write out the match found. You need to change Field to your database field you are search (its in red)
Response.Write(rsSearch("Field") & "<br>")

'Move to next line in database
rsSearch.MoveNext
'Continue looping through database to display all results found
Loop
End If

note: as we open the database we had to corresponding action to do to close the database

'Reset server objects
Set rsSearch = Nothing
adoCon.Close
Set adoCon = Nothing
%>

JDBC has four primary pieces, used for each database access phase:

• DriverManager: the DriverManager class loads and configures a database driver on the database
• Connection: the Connection class performs confectioning and authentication to a database

The usual password and username of a database especially the oracle

• Statement / PreparedStatement: the Statement and PreparedStatement classes send SQL statements to the database engine for preprocessing and eventually execution

…..

• ResultSet: the ResultSet class allows for the inspection of results from executions

Here some sample code for you:

here some more example links for you:

http://www.javacoffeebreak.com/articles/jdbc/

http://www.acm.org/crossroads/columns/ovp/march2001.html

First I installed unixodbc and tdsodbc packages.  Then I mainly followed the instructions here starting at the "Configuration" part.  These were the key, because in my ignorance I tried editing odbc.ini directly and was also looking at /etc/freetds/freetds.conf which I don't think is actually used when running with ODBC.

I can now use:-

isql <dsnname> <username> <password>

...and get a console to type arbitrary SQL in.  I tried using OpenOffice.org's oobase, and although it connects and shows me a list of tables, it can't seem to query any of them due to malformed SQL.  I'm not sure where the problem lies, but I was just experimenting.

Ideally I'd like to find something a bit like SQL Server Management Studio Express as a front-end, because I use that a lot.  I run a work site hosted on ASP.NET with a MSSQL backend, and I often have to run raw SQL to get around the lack of proper admin pages because the lazy developer (i.e. me) hasn't written them yet.

While browsing package lists, I spotted mention of GNOME Data Access (gda) which has a freetds backend, so I will check that out too.

More links:-

• http://www.freetds.org/userguide/freetdsconf.htm
• http://www.unixodbc.org/doc/FreeTDS.html
• http://www.freetds.org/userguide/odbcconnattr.htm

What made this one comical to me is that the monitor that this ODBC setup was taking place on was a giant flat panel monitor hanging above the baggage claim carousel in the Wichita airport.

Dude...next time you might want to turn off that screen before you go advertising your database server's name and other info to everyone waiting on their luggage!

And yes...I blacked out the server name...just in case. I really don't want a visit from Homeland Security! Although honestly, the picture was such low resolution that you couldn't make it out anyway.

So i assume you know the basic....first create a module

Public goConn As New ADODB.Connection

Public Function DataOpen(oConn As Connection) As Boolean
'On Error GoTo Open_EH

oConn.CursorLocation = adUseClient

' Set the connection string by calling
' a function.
oConn.ConnectionString = ConnectString()

' Set the mode of the connection
oConn.Mode = adModeReadWrite

' Open the Connection
oConn.Open

DataOpen = True

Exit Function

Open_EH:

' Call ErrorHandler(goConn)
'DataOpen = False
'Exit Function
End Function

Public Function ConnectString() As String
' SQL Server using an ODBC Data Source
'ConnectString = "DSN=EmployeeSQLServer;" & _
' "UID=sa;PWD=;" & _
' "DATABASE=Employees"

' SQL Server using OLE DB Provider
'ConnectString = "Provider = sqloledb;" & _
' "Data Source = (local);" & _
' "Initial Catalog = Employees;" & _
' "User Id = sa;" & _
' "Password = ; "

' Jet MDB
ConnectString = "Provider=Microsoft.Jet.OLEDB.3.51" & _
";Data Source=" & App.Path & "..adoEmployees.mdb"
End Function

we are using Microsoft jet OLEDB to retrieve data which only work with Microsoft access database which is not as good as other ODBC and OLEDB .....

"GOCONN" is our connection.....

Now we will create two forms....one through which we connect to our database and second in which we show data..check the snaps for idea

now in form2 on "connect to database" button event paste this code

Private Sub Command1_Click()
Dim boolPerform As Boolean

Screen.MousePointer = vbHourglass

' Open the Database Engine
boolPerform = DataOpen(goConn)

If boolPerform Then
Form1.Show
End If

Screen.MousePointer = vbDefault

End Sub

and in form 1...paste this code on show event button

Private Sub Command1_Click()
Dim oRS As Recordset
Dim strSQL As String

strSQL = "SELECT "
strSQL = strSQL & "szLast_nm, "
strSQL = strSQL & "sFirst_nm "
strSQL = strSQL & "FROM tblEmployees "

Set oRS = New Recordset
oRS.Open strSQL, goConn, _
adOpenForwardOnly, adLockReadOnly
Do Until oRS.EOF
lstNames.AddItem oRS("sFirst_nm") & _
" " & oRS("szLast_nm")

oRS.MoveNext
Loop
oRS.Close

End Sub

ok the coding is done.... Also set your startup object to FORM2 by going in project menu bar then project properties......we will show form2 first to connect to data base if it could not connect to database it will show an error otherwise show form1...

Kies een tabblad om de ODBC in te maken. Met het tabblad System DSN kunnen alle systemen de ODBC-koppeling gebruiken. Met UserDSN kun je users rechten geven dit te gebruiken

Kies Add voor toevoegen, Remove voor verwijderen en Configure voor bewerken.

Kies Client Acces ODBC Driver (32-bit)

Geef de naam voor de koppeling aan in het vak Data Source name
Geef de servernaam aan, of het IP adres aan in het vak System.

Typ in het vak Library list de bibliotheken die je wil gebruiken, hier kunnen er dus meerdere tegelijk worden ingevoerd.

Geef de juiste bibliotheek aan in het vak Package library

Gegevens van de ODBC koppeling worden opgeslagen in registry keys en in C:winntodbc.ini. Roep de registry key op via regedit: HKEY_CUrrent_userSoftwareODBC

Exporteer een gemaakte registry key via Registry, Export registry file.

Het is ook mogelijk om deze gegevens verder in de applicatie waar ze naar toe zijn gehaald te bewerken. Zo kun je met ODBC-koppelingen gegevens naar Excel overhalen en hiermee een draaitabel of draaigrafiek maken.

Op dit moment heb ik op mijn werk gegevens uit een AS400 machine overgehaald naar Excel, waarin via een parameterquery een bestand met een bepaald soort gegevens wordt geselecteerd. Aan dit Excel bestand hangt een samenvoegbrief, zodat alle gegevens die voldoen aan de voorwaarden in een brief worden geïmporteerd. Op deze manier opent men een Excel bestand, geeft aan waar op gezocht moet worden, opent de samenvoegbrief en de brief wordt na tweemaal een klik op samenvoegen keurig gemaakt. Het enige nadeel dat ik nu heb ondervonden is dat alle Office applicaties eerst volledig moeten worden afgesloten voor gebruik en nogmaals alles afsluiten na gebruik. Misschien dat er nog een handige ODBC-kenner mij nog eens een tip aan de hand kan doen.

Thus AIS Web was born, a Microsoft .Net Web Application which would allow the development team to more rapidly respond to users requests for funtional enhancements to the application. No components would reside on the users client computer. The existing database would remain and would have minimal modifications.

The application was written in C# to leverage the existing skills of the development team. Connections from the Web Server to the Database server were established via ODBC as the existing third party Database supplier and drivers did not support ADO.