[Fwd: Creating an ODBC Driver with Forte]

Has anyone created an ODBC driver with Forte? The Microsoft ODBC
Software Development Kit (SDK) assumes that ODBC drivers will be
developed in C. I would like to write the driver in Forte TOOL. Even
though C++ code can be generated from TOOL code, I am not certain that
the generated C++ code will conform to the ODBC API, and be compatible
with other ODBC components, such as the ODBC Driver Manager, ODBC
Installer, and ODBC Test applications supplied by Microsoft with the
ODBC SDK. Any advice would be appreciated. (The purpose of my ODBC
driver is to enable data access by any ODBC client application, using
calls to Forte service objects to retrieve and process the data before
it is sent to the client application.)
Chris Johnson
Unified Information, Inc.
425-814-4007
MailTo:[email protected]

The following is extracted from Oralce's Metalink: (sorry lost the link)
"This is an NLS related issue. The ODBC driver uses the values derived from the NLS_LANG setting from the Oracle Home where the driver is installed.
The application actually uses the number setting from the NT Regional Settings.
When these two settings differ, then the decimal character will be cut off. This behaviour is also described in Bug:694323.
Example:
You have set your NLS_LANG in the ORACLE_HOME of your ODBC driver to GERMAN_GERMANY.WE8ISO8859P1. This will result in a value for the NLS_NUMERIC_CHARACTERS of ",." (the first part of the NLS_NUMERIC_CHARACTERS being the decimal character and the second part being the group separator).
So the "." is used by the Application and the "," is used by the Oracle ODBC driver.
As a result numeric values in your Oracle Database with an integer and a decimal part will thus be displayed by the application without the decimal character, i.e. a value of 10,734 will be displayed as 10734 a value of 0,123 will be displayed as 123.
To fix this, you will either have to correct the character used for the Decimal Symbol of your NT Regional settings to match the value of your Oracle NLS_LANG setting or vice versa. To change the value for NLS_LANG, go to your registry and change the NLS_LANG parameter that is situated under HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE/HOMEnnn/NLS_LANG where HOMEnnn is the home where your Oracle ODBC driver is installed."
Hope this helps, resolved our issue with this problem.

Similar Messages

Oracle 10g ODBC driver with Windows 7 32 bit connecting to Excel

Hi Everyone,
I'm having an issue connecting to our oracle 10g database (64 bit system) from a 32 bit windows 7 installation running excel 2010/2007 using odbc drivers. Our excel spreadsheets worked without issue in windows xp.
In windows 7 I have been able to install the odbc driver via the following method:
1. Download the oracle 'basic' client and oracle 'odbc' client from www.oracle.com and extract the contents:
instantclient-basic-win32-10.2.0.3-20061115
instantclient-odbc-win32-10.2.0.3-20061115
2. Create a folder 'oracle' and place the instantclient_10_2 folder inside.
3. Ensure all the basic and odbc files reside in this folder.
4. Create a 'network' folder within instantclient_10_2
5. Create an 'admin' folder within 'network'
6. Create sqlnet.ora and tnsnames.ora files within the 'admin' folder:
7. Run 'obdc_install' within the instantclient_10_2 folder
8. Download and run the oracle odbc driver exe file from www.oracle.com (ORA10203.exe)
9. Go to Control Panel -> Administrative Tools -> Data Sources and create a new System DN
This allows excel spreadsheets connecting ONLY to oracle to function.
Unfortunately some of our spreadsheets connect to both a MySQL database as well as oracle. Spreadsheets connecting only to MySQL also function correctly, however, as soon as the vb associated with a spreadsheet includes a mysql call followed by an oracle call the spreadsheets fail. In Excel 2007 excel crashes completely everytime. In Excel 2010 the mysql data is generated, then when the script hits to oracle odbc connection there is a long pause, the oracle ODBC driver connect pops up requesting a username/password (this didn't happen in xp), then the data source selection pops up, then the username/password connect screen pops up again, and finally it fails with a runtime error '1004' General ODBC error.
If you look at the VB script it's failing at the Refresh BackgroundQuery statement in the ODBC connection block:
With Worksheets("Oracle1").QueryTables.Add(Connection:= _
"ODBC;DSN=Oracle_ODBC;UID=user;PWD=password;SERVER=ORACLE_LINUX;", _
Destination:=Worksheets("Oracle1").Range("A1"))
.CommandText = strSql
.Name = "Oracle1_data"
.FieldNames = True
.RowNumbers = False
.FillAdjacentFormulas = False
.PreserveFormatting = True
.RefreshOnFileOpen = False
.BackgroundQuery = True
.RefreshStyle = xlOverwriteCells
.SavePassword = True
.SaveData = True
.AdjustColumnWidth = True
.RefreshPeriod = 0
.PreserveColumnInfo = True
.Refresh BackgroundQuery:=False
End With
Does anyone know how to get around this? It's very important!!
Also if you try to edit the oracle ODBC connections in Control Panels -> Administrative Tools -> Data Sources, ODBC crashes 95% of the time.
Advice greatly appreciated!!

Well, here's what I'd check anyway..
1) get Process Explorer from http://sysinternals.com
2) make a mysql connection, get a list of dll's loaded (include the location and version columns in the lower pane output)
3) close that, then make an ora odbc connection, get a list of dlls.
4) close that, then make a mysql connection followed by an ora odbc connection, get a list of dlls
5) compare the lists of loaded dlls. In particular, the difference between #3 and #4, is there a dll dependency that gets loaded by oracle's odbc that comes from a different location when you've opened a mysql connection first?
May or may not help, but might turn up a difference to help point you in a direction.
Greg

ODBC driver with Oracle 10G on 64bit Windows OS.

I m facing a issue with my peoplesoft application which is installed on Windows 2003 64bit OS.
Setup Details
Oracle 10G Server on AIX 5.3.
peoplesoft CRM tools 8.48,Oracle 10G client in on Windows 2003(64bit) installed.
When i open ODBC administrator from CRM its open showing all the drivers registred to 64bit registry. Whereas when i see ODBC admin from Control panel of OS , its showing driver register from 32bit. My observation is that oracle ODBC driver is getting registerd with 32bit and application is calling DDBCadmin of 64 bit. Hence driver is not getting registered with 64bit registry.
sqora32.dll..
Regards
Alok

Hi kamlesh,
Thanks for your help, still i am not clear about installation on both nodes. once you install CI on one node you are giving the path of shared disk and if we go for other node then also we need to give the shared disk path : so will it or any other? if it is then alrady one usr and aracle folder exists after node A installation. Do you mean to say copy usr and oracle folder? please explain in detail, will be higly appreciable.
Bye,
Nizam

ODBC Driver with Access problem

I have problems with fields of the number(9.3) datatype. in my linked access tables numbers like 1555.33 are shown as 155533.
I'm using the oracle odbc driver version 9.2.0.54 with a 9i (9.2.0.1.0) Database.
I've reading at an old post called "number(9.3) DataType in MS Access". Where I've found someone with the same problem as me. I've done everythink which is explained on that message, but it still doesn't work.
Is there anything else to do?
Thank you in advance!

The following is extracted from Oralce's Metalink: (sorry lost the link)
"This is an NLS related issue. The ODBC driver uses the values derived from the NLS_LANG setting from the Oracle Home where the driver is installed.
The application actually uses the number setting from the NT Regional Settings.
When these two settings differ, then the decimal character will be cut off. This behaviour is also described in Bug:694323.
Example:
You have set your NLS_LANG in the ORACLE_HOME of your ODBC driver to GERMAN_GERMANY.WE8ISO8859P1. This will result in a value for the NLS_NUMERIC_CHARACTERS of ",." (the first part of the NLS_NUMERIC_CHARACTERS being the decimal character and the second part being the group separator).
So the "." is used by the Application and the "," is used by the Oracle ODBC driver.
As a result numeric values in your Oracle Database with an integer and a decimal part will thus be displayed by the application without the decimal character, i.e. a value of 10,734 will be displayed as 10734 a value of 0,123 will be displayed as 123.
To fix this, you will either have to correct the character used for the Decimal Symbol of your NT Regional settings to match the value of your Oracle NLS_LANG setting or vice versa. To change the value for NLS_LANG, go to your registry and change the NLS_LANG parameter that is situated under HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE/HOMEnnn/NLS_LANG where HOMEnnn is the home where your Oracle ODBC driver is installed."
Hope this helps, resolved our issue with this problem.

Oracle7 ODBC Driver with an Oracle 8 database

Does anybody know if there are any issues with using an Oracle 7 ODBC driver to access information on an Oracle 8 database?

Assuming you have an Oracle 7.3.4 client with the Oracle 7 ODBC driver, you're probably fine connecting to any of the current database releases. Since Oracle7 was desupported a while ago, however, there's no guarantee that this will continue to be the case as time goes on. Additionally, you probably won't be able to get support if you run into problems with this configuration.
Justin

ODBC Driver with VC++ Application

Problem description.
For example if we are reading the EMP table with the following SQL,
select * from emp order by empno;
Step 1: We are reading the EMPNO = 7369 (1st Record)
Column COMM value read will be NULL
Step 2: After that when we read EMPNO = 7499 (2nd record)
Column COMM value read will be 300
Step 3: After that when we read EMPNO = 7521 (3rd record)
Column COMM value read will be 500
Step 4: After that when we read EMPNO = 7566 (4th record)
Column COMM value read will be 500 even though there is no value for COMM in the table.
Please note that we will not be able to change the Application code for this problem resolution.
We request you to give us some solution ASAP.
Should you have doubts in the information sent by us, please do revert back for clarifications.

Dear Justin,
Thanks for the reply and the information.
I am trying from Oracle support.
But any way I will answer your Questions.
Qus 1. What version of the Oracle ODBC driver are you using?
Ans 1. I can use both Oracle driver and Microsoft Driver.
Versions: Oracle ODBC Driver: 8.01.07.00
Microsoft Driver for Oracle: 2.575.1022.00
Qus 2.Did you try applying the latest patch set?
Ans 2.I have tried but it did not work. i.e. Problem continued.

Oracle ODBC driver with Access Application

I get a problem when using MS-Access 2007 DAO recordset built on table hosted by an Oracle database 10g and connected thru ODBC
The table scheme is :
idPartenaire : number(11)
libelle : varchar2(250)
code : varchar2(5)
actif : number(1)
idCollege :numner(11)
idPartenaire is generated by a sequence read in a trigger fired before insert on th table.
The code I use in Access is :
The query associated with the form is :
"select * from table1"
and the event procedure connected to a button on the form is :
Private Sub Commande0_Click()
Dim rs As DAO.Recordset
Me.Recordset.AddNew
Me.Recordset!libelle = CStr(Rnd) ' some value
Me.Recordset!code = “”
Me.Recordset!actif = -1
Me.Recordset!idCollege = 1
Me.Recordset.Update
Me.Recordset.Bookmark = Me.Recordset.LastModified
Dim idtemp As Long
idtemp = Me.Recordset.idPartenaire
Me.Requery
Me.Recordset.FindFirst "idPartenaire = " & idtemp
Set rs = Nothing
End Sub
When I run this code, I get an error 3167 (current record is deleted) on the line :
idtemp = Me.Recordset.idPartenaire
If I change the ligne :
Me.Recordset!code = “”
By :
Me.Recordset!code = “xxxx”
or if I comment this line, the error does not appear and I get the right value in idtemp variable.
I tried also with the same table in a SQL Server database table. In this case it works fine in all cases.
So, I seems that the problem is due to the Oracle ODBC driver. I tried with different versions of Oracle ODBC drivers (v10.0.2.4, v11.1.6)
I search on Internet but I have not found any explanation or solution.
Does anybody experiment the same problem (and find a solution)?
Gilles Roussel.

The two lines you quote aren't errors, they're warnings and they're pretty standard fare. If there isn't anything else in the ODBC log, then the driver isn't returning any errors. I'm not sure why Access is failing, so let's look at the client configuration first.
- I assume you've successfully installed the 8.1.6 client on the machine with Access. Were there any errors during the install?
- You say you're using the 8.1.6 version of the Oracle ODBC driver-- can you look to see what the last digit of the version is? If possible, I'd start by downloading the most recent 8.1.6.x ODBC driver from OTN.
- Check which version of the MDAC you have installed (new versions & a version checker are available from Microsoft at <http://www.microsoft.com/data>.
- The ODBC driver you download above will list which versions of the MDAC it is expected to work with. Make sure your version is one of the listed versions.
Justin

Can you create an ODBC connection with a VI ?

One VI came up when I searched example code; however, it had problem with loading a VI (see attached) and seemed limited. I wanted to be able to create an ODBC for connecting a SQL Server database that is hosted on the network.
Attachments:
load_window_error.gif ‏4 KB

Your error message states that your VI has no block diagram, so it could not convert to LV 7. It must have been saved with the option to not include the block diagram.
To answer your question about ODBC, I believe you need the Database Connectivity Toolset, comes with Enterprise Toolset or Toolkit, to make database connections and SQL queries. It works well and is worth the extra money. Visit NI website to learn more about this toolset.
- tbob
Inventor of the WORM Global

Can I create a raid drive with disk utility

I recently bought a 2TB seat gate external drive.
I want to use this drive with time machieve as well as set it up as a raid drive to strode photos.
Is this possible to do with disk utility?

Hello
you can not make any kind on RAID type with only one hard drive you need at least tow drive to perform a RAID volume
then , hard drive utility can be use to perform software raid ( Level 0 an Level 1 only )
for more info about RAID technologie http://en.wikipedia.org/wiki/RAID
Pierre

If I create an external drive with Yosemite that I can boot from, will I also be able to boot from my internal drive still?

So I am still on Mountain Lion and I haven't upgraded because I have always been worried that Logic Pro, my Plug ins, and my Hardware wouldn't work right on the new OSX. I am now becoming interested in upgrading since Logic has a new update that I cant use.
My plan is to install Yosemite on an external drive that has thunderbolt connection so that I can boot from that and give everything a trial run. Is this something that actually works? If I do this, and things arent compatible on Yosemite, will I be able to boot from my internal and be back on Mountain Lion as I am now?
Thanks!

External drive must be partitioned and formatted for Mac OS Extended, Journaled.
Clone Yosemite, Mavericks, Lion/Mountain Lion using Restore Option of Disk Utility
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
     1. Select Disk Utility from the main menu then press the Continue
         button.
     2. Select the destination volume from the left side list.
     3. Click on the Restore tab in the DU main window.
     4. Select the destination volume from the left side list and drag it
         to the Destination entry field.
     5. Select the source volume from the left side list and drag it to
         the Source entry field.
     6. Double-check you got it right, then click on the Restore button.
Destination means the external drive. Source means the internal startup drive.

ODBC with Forte

Has anyone built an application using ODBC with Forte? We are in the
process of doing this but have no clear understanding of what we have to
do to use ODBC. Do we get rid of all the SQL we have created? Do we
by-pass Forte's database access functions? I have called Forte on this
issue. They simply pointed me to the Accessing Database book which
simply pointed out how to set the ODBC driver.
Thanks!
Maria Lim
May & Speh
1501 Opus Place
Downers Grove, IL 60515
630-971-4758
[email protected]

At 11:41 AM 1/6/98 -0600, you wrote:
Has anyone built an application using ODBC with Forte? We are in theMaria,
In response to your inquiry regarding ODBC use with Forte.
Accessing a database via ODBC with Forte is no different than accessing it
using native drivers. I've used ODBC to work with MS Access, MS SQLServer
and IBM's DB2 (via a third party ODBC driver).
The following assumes you want to use the ODBC driver in a server partition.
If you want to use it from a client (Win 3.1x, Win95) ask tech support
for TECHNOTE 10540, "Configuring and testing ODBC on Windows 3.11/95/NT with
Oracle, SQLServer, and Access."
The steps to access ANY database within Forte are the same regardless of
the drivers used (ODBC vs. native drivers).
First: Install the database in the target machine. If the database will be
accessed via an ODBC driver, then you must define the driver (in NT it is
done from the ODBC icon in the control panel). The data source name will
be the database name you'll use in the Forte DBSession object.
Second: Tell the Forte environment that there is a database resource in the
node where you defined the ODBC database. One way to do this is via Econsole.
You would lock the environment and update the node properties to add an ODBC
resource. The resource name will be the DatabaseManager name in the
Forte DBSession object.
Third: Create a DBSession using the resource manager name and data source
name you created.
Fourth: Write Forte code to use the database. Sometimes the SQL syntax between
databases differs (specially if you are using functions, etc.) so you may
have to
allow for that if you are converting between databases.
Good luck
Gabriel J. Choza
Forte Technical Sales
(602) 553-1029
2390 E. Camelback - Suite 300
Phoenix, AZ 85016

Oracle 10g Express Edition Beta 3 ODBC Driver Always Crashes

I find that if you set up an ODBC Data Source for Oracle 10g Express Edition on Windows XP SP2 using the "Oracle in XE" driver, anything that tries to access it will crash, even the Windows ODBC Data Source Administratior if you click the "Test Connection" button.
Having clicked the button, you get a window coming up entitled "Oracle ODBC Driver" with a yellow exclamation mark in it, with no other text in the window except for an OK button.
If you press OK, then it crashes and goes through the "Please tell Microsoft about this problem" process....

Hi,
Thanks for your comment, but I can't get onto the XE forum.
I found http://www.oracle.com/technology/products/database/xe/forum.html which says:
Forum registration is possible only by downloading and installing Oracle Database XE. After installation, click on the "Registration" link from the Database homepage.
However I find that the "Database Homepage" does not exist.
Choosing the Oracle XE "Go To Database Home Page" takes my browser to http://127.0.0.1:8080/apex which is not available even though my oracle server is running and sqlplus can talk to it.
There's definitely nothing serving on tcp port 8080, as follows:
[dcampbel@clevo]~> telnet localhost 8080
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
Regards,
-- Dave

ODBC Driver 8.1.7.3 - pending bugs?

Does somebody know if the problem below has been fixed with Oracle ODBC 8.1.7.3 driver for NT?
Version 8.1.7.2.0 of the Oracle ODBC driver (with Net8 8.1.7.0.0) tends to fail with multithreading application, running only on a single processor. Therefore we do not recommend it. The failure typically occurs as a conversion error ("ORA-01461 can bind a LONG value only for insert into a LONG column" or "ORA-01460 unimplemented or unreasonable conversion requested").
Gisella Saavedra
null

My e-mail is [email protected]
I guess I have not updated my profile for a while.
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Gisella Saavedra ([email protected]):
Does somebody know if the problem below has been fixed with Oracle ODBC 8.1.7.3 driver for NT?
Version 8.1.7.2.0 of the Oracle ODBC driver (with Net8 8.1.7.0.0) tends to fail with multithreading application, running only on a single processor. Therefore we do not recommend it. The failure typically occurs as a conversion error ("ORA-01461 can bind a LONG value only for insert into a LONG column" or "ORA-01460 unimplemented or unreasonable conversion requested").
Gisella Saavedra
<HR></BLOCKQUOTE>
null

Oracle ODBC Driver adds bind variable when browsing whole table in Access

Hi, we are looking for some reasons why we may see this behavior in the Oracle ODBC driver (10gR2 and 11g) when using Microsoft Access (2003 or 2007)...
1) Link a table from the Oracle database.
2) Double-click the newly linked table to "browse" it.
Oracle sends the following statement to the server:
{color:#0000ff}select * from linked_table where primary_key = :b1{color}
It then proceeds to read the entire table.
If I tell Microsoft Access that there is no primary key, the query gets sent as:
{color:#0000ff}select * from linked_table{color}
And the query comes back as soon as the first 100 or so rows are fetched which is quite quickly.
ADDITIONAL NOTES:
1) If the table has a primary key or unique constraint, Microsoft Access automatically assigns that as the primary key.
2) We can stop the behavior in #1 if we wrap a view around it which prevents Access from discovering that information and then it prompts for a primary key definition.
3) If we use the Microsoft ODBC driver, the bind variable is not added no matter what the primary key defintiion is.
We're stumped and are looking for solutions and/or workarounds without having to wrap all of our tables in views to hide the fact that there is a primary key.
Thanks,
Steve

Thanks for the response, Greg.
The specific question I am seeking an answer for (sorry it was not clear on my first message) is this:
Why does the Oracle driver add the bind variable to the query only when the primary key is defined?
The Microsoft ODBC driver does not add the bind variable with or without a primary key defined.
You asked how I traced this statement and what I am doing is launching the query in Access and then using TOAD to view the V$SESSION and V$SQL_TEXT_WITH_NEWLINES views. All I do is change the driver. This is just for a simple browse table (double-click on the table) which should send
select * from table
However, whenever I use the Oracle ODBC driver (with a primary key defined) it sends
select * from table where primary_key = :1
If I remove the primary key on the table definition, the Oracle driver sends
select * from table
What is it about the primary key that could cause that behavior?
I don't think it is the MDAC/Jet level because this is the conversion to the native SQL statement not the Jet version. I know the Oracle driver has to do that part because you have those workaround options like don't add the RULE hint, etc. That's not part of the Jet engine.
Hope that helps. I'm just baffled over this one and wish I knew where to go next.

ODBC failure with plsql

I have Oracle9i Client 9.0.1.1.1 and Oracle ODBC Driver 9.1.0.1 installed. When I connect to the remote database with the ADODB activex object with this driver, I get different results running the ADODB.execute command on a plsql procedure depending on the version of the database I am connecting to.
If I am connecting to an Oracle9i 9.2.0.1.0 database, the plsql executes successfully. If I am connecting to an Oracle8i 8.1.7.2.0 database, the plsql fails.
Running the ODBC trace gives two different syntaxes for the different calls also.
Oracle9i 9.2.0.1.0 shows:
Processid:{3D14 714-7d8     ENTER SQLExecDirectW
          HSTMT 00A54850
          WCHAR * 0x024D0E50 [     131] "{ call intp.bline_str_create.createStr(2003, 'VCO', 'W', 'C108010102', 'test', 'C.1.08.01.01.02.CC', 'OE', '062690', '', '', 'F') }"
          SDWORD 131
Processid:{3D14 714-7d8     EXIT SQLExecDirectW with return code 0 (SQL_SUCCESS)
          HSTMT 00A54850
          WCHAR * 0x024D0E50 [     131] "{ call intp.bline_str_create.createStr(2003, 'VCO', 'W', 'C108010102', 'test', 'C.1.08.01.01.02.CC', 'OE', '062690', '', '', 'F') }"
          SDWORD 131
while Oracle8i 8.1.7.2.0 shows:
Processid:{3D14 714-7d8     ENTER SQLExecDirectW
          HSTMT 00A54CD8
          WCHAR * 0x024D8728 [     114] "idaho.ifpapk_manage_task.add_task('COS', 568, 'C.1.08.01.01.02.A1', 'test', 'test', '09/30/2002', '01/01/4712', 0)"
          SDWORD 114
Processid:{3D14 714-7d8     EXIT SQLExecDirectW with return code -1 (SQL_ERROR)
          HSTMT 00A54CD8
          WCHAR * 0x024D8728 [     114] "idaho.ifpapk_manage_task.add_task('COS', 568, 'C.1.08.01.01.02.A1', 'test', 'test', '09/30/2002', '01/01/4712', 0)"
          SDWORD 114
          DIAG [37000] [Oracle][ODBC][Ora]ORA-00900: invalid SQL statement
(900)
Please help.

My mistake on the ODBC Driver Verion number - Sorry. I was using the Oracle ODBC Driver version 9.0.1.0.1. We upgraded to the 9.0.1.5 Oracle ODBC driver with no success.
The Oracle 8.1.7.2 database I am connecting to in the failed instance is not willing, at this time, to upgrade. It is in their plans for the future which doesn't help me.
The syntax for the failing call to the PLSQL is:
opConn.ConnectionTimeout = 60;
     opConn.CommandTimeout = 60;
     opConn.Open(Session("OP_ConnectionString"),
Session("OP_User"),
Session("OP_Password"),
     strQuery2 = "idaho.ifpapk_manage_task.add_task('"
                    + usernameU + "', " + proj_id + ", '"
                    + tt_number + "', '" + tt_name + "', '"
                    + tt_description + "', '"
                    + tt_start_date + "', '"
                    + tt_completion_date + "', "
+ cn_parent_task_id + ")";
opConn.Execute(strQuery2);
I know the connection is getting made - I can perform a Select statement successfully.
Thanks.

[Fwd: Creating an ODBC Driver with Forte]

Similar Messages

Maybe you are looking for