Data Access Worldwide Forums - Data Connectivity http://support.dataaccess.com/Forums/ en Wed, 22 May 2013 08:48:07 GMT vBulletin 60 http://support.dataaccess.com/Forums/images/misc/rss.png Data Access Worldwide Forums - Data Connectivity http://support.dataaccess.com/Forums/ Welcome to the CLI Connectivity Kits version 6 - Beta Program! http://support.dataaccess.com/Forums/showthread.php?50594-Welcome-to-the-CLI-Connectivity-Kits-version-6-Beta-Program!&goto=newpost Fri, 17 May 2013 20:33:56 GMT Data Access is pleased to announce the availability of the CLI Connectivity Kits version 6!

Major Changes in CK6

 Support for all MS SQL Server 2008/2012 types, including the new date, datetime2, and time types
 Support for all IBM DB2 10.1 types
 Configurable mapping from DataFlex types to SQL types
 Improved restructure logic
 Auto-reconnect after lost connection

The Data Access CLI Connectivity Kits version 6 Beta contains the following Connectivity Kits:

 SQL Server Connectivity Kit 6.0
 ODBC Connectivity Kit 6.0
 DB2 Connectivity Kit 6.0 for Windows
 DB2 Connectivity Kit 6.0 for Linux

The Data Access CLI Connectivity Kits version 6 Beta is delivered as a zip file, without an installer.
The components have to be copied manually to the DataFlex or Visual DataFlex folders.

Download the CK6 Beta 1

Read the instructions on how to Install CK6 Beta 1

Read the complete What's New


The Data Access Worldwide Development Team ]]> Data Connectivity Stephen W. Meeley http://support.dataaccess.com/Forums/showthread.php?50594-Welcome-to-the-CLI-Connectivity-Kits-version-6-Beta-Program! Connect a CM 3.2 app on Linux to MSSQL http://support.dataaccess.com/Forums/showthread.php?50589-Connect-a-CM-3.2-app-on-Linux-to-MSSQL&goto=newpost Fri, 17 May 2013 12:27:15 GMT CM 3.2 on Linux. We want to connect to a MSSQL Server. I'm thinking we can configure a connection to the server using unixODBC and FreeTDS. I know the DAW CK on Linux supports DB2. But we want to connect to a MSSQL database. Possible? ]]> Data Connectivity chuckatkinson http://support.dataaccess.com/Forums/showthread.php?50589-Connect-a-CM-3.2-app-on-Linux-to-MSSQL Error 75 after Mertech to MSSQL http://support.dataaccess.com/Forums/showthread.php?50559-Error-75-after-Mertech-to-MSSQL&goto=newpost Tue, 14 May 2013 11:55:00 GMT Hi all, i tried to convert our Software from dataflex to mssql with the Mertech Flex2SQL 12 driver. After the convertion finished without errors,... Hi all,

i tried to convert our Software from dataflex to mssql with the Mertech Flex2SQL 12 driver.
After the convertion finished without errors, the programm throws an error 75 (cant open .dat file) when im trying to start it.
Im new to mertech so im a little bit clueless.

I hope someone could help me out there ;)


greetz
Micha ]]> Data Connectivity Micha http://support.dataaccess.com/Forums/showthread.php?50559-Error-75-after-Mertech-to-MSSQL VDF Fail-over http://support.dataaccess.com/Forums/showthread.php?50534-VDF-Fail-over&goto=newpost Fri, 10 May 2013 07:51:13 GMT Now, we realise what we're looking at is pretty unusual...

The app is using a global database connection which is specified in MSSQLDRV.Int as DAW suggest.

We are looking into the possibility of having the app fail-over to another database on a different database server if the primary one against that app goes down (can't be connected to) regardless of whether it was running when the app was opened or goes down mid-transaction etc.

In a nutshell, we require some automatic way of failing-over the app to a different database server and database should the primary one go down. This is over and above MSSQL Replication functionality.

From memory there is a time-out or something in the driver. But whether we can trap that I am not sure.

Has anyone done anything of this nature before? got ideas??? ]]> Data Connectivity kelly http://support.dataaccess.com/Forums/showthread.php?50534-VDF-Fail-over Pervasive Question http://support.dataaccess.com/Forums/showthread.php?50476-Pervasive-Question&goto=newpost Thu, 02 May 2013 09:35:17 GMT We're testing Pervasive in a multi-language enviroment.

We see the correct text in VDF (even after saving and refinding the record) but in Pervasive we see rubbish (see screenshot) regardless of what combination or code page we have set.

We need Arabic code page for this particular test.

Are we missing something?

I came across this in the Pervasive help but it doesn't mean anything to me.

Quote:
OEM/ANSI Conversion
This setting allows applications to store or
retrieve character data in any OEM character set using Pervasive PSQL, while
allowing the data to be manipulated and displayed using the ANSI Windows
character set.

The Pervasive ODBC driver translation DLL can
perform all necessary translations between the two character sets. This feature
can be turned on or off for each DSN. Any character data that is passed to and
from the database is correctly translated by the ODBC driver between the OEM and
ANSI character sets.

The Pervasive PSQL Control Center (PCC) uses the
JDBC driver. The JDBC driver is unaware of the OEM to ANSI translations. If you
have OEM data that you want to view in PCC, set the properties of the database
to use character encoding IBM437.

If your application connects to the data source
using SQLDriverConnect, you can also specify the translation DLL using the
connection string option TRANSLATIONDLL=path_and_DLL_name. The translation DLL name for Pervasive
PSQL is W32BTXLT.DLL.

Note
The OEM-to-ANSI translation option is
available only for client or local Engine DSNs. It is not available when setting
up a remote Engine DSN.
The DLL ( W32BTXLT.DLL) as suggested above doesn't exist on our server.

Can someone please tell me what has to be done to make it work...

We're using Pervasive v11 on a 64 bit 2008 R1 Windows Server along with VDF 17.1 B2.

TIA
Attached Thumbnails
Click image for larger version Name: Pervasive.png‎ Views: N/A Size: 71.7 KB ID: 6415   Click image for larger version Name: VDF - Working.png‎ Views: N/A Size: 49.1 KB ID: 6416  
]]> Data Connectivity kelly http://support.dataaccess.com/Forums/showthread.php?50476-Pervasive-Question Pervasive Test Connection Error http://support.dataaccess.com/Forums/showthread.php?50469-Pervasive-Test-Connection-Error&goto=newpost Wed, 01 May 2013 08:56:20 GMT I've got the pervasive driver loaded and pervasive configured with a user name + password but I'm still getting this error.

Anyone got any idea what causes it?

Google isn't helpful to me.

EDIT- and I also added the below to the DFBtrDrv.int file in the bin folder of VDF - program files x86 (assuming that was where Martin meant to make the change).

DATABASE_MODE 1

A copy is attached (had to change the file extension to .txt so could post on here).
Attached Thumbnails
Click image for larger version Name: Error.png‎ Views: N/A Size: 15.6 KB ID: 6405  
Attached Files
]]> Data Connectivity kelly http://support.dataaccess.com/Forums/showthread.php?50469-Pervasive-Test-Connection-Error Limitations on PSQL to MSSQL conversion http://support.dataaccess.com/Forums/showthread.php?50452-Limitations-on-PSQL-to-MSSQL-conversion&goto=newpost Mon, 29 Apr 2013 05:25:02 GMT Hi All, Due to popular demand we have to move from PSQL to MSSQL. Peace of cake ... run the conversion tool and we are done. WRONG The... Hi All,

Due to popular demand we have to move from PSQL to MSSQL.
Peace of cake ... run the conversion tool and we are done. WRONG

The conversion takes a lot more time because of the limitations of MSSQL in the department of index creation and the support of overlap fields.
The limitation i'm running into is the 16 column maximum of an index in MSSQL even when an index-length of 900 bytes is possible. Correct me if i'm wrong...

In PSQL there is also a limitation of 255bytes per index. I only twice hit this maximum in one of my apps. The number of index columns is not limited.
Overlap-fields were used to group columns into usefull names, so that indexes containing for example 25 columns into 4 overlap-fields.

This technic does not work in MSSQL. Overlap-fields, although defineable via INT, can not be used in an index (an overlap-fields containing of 4 columns gets converted to 4 columns in an index)
As you can image i'm running out of real-estate index-wise pretty fast. In fact i don't think i can transfer our applications to MSSQL from PSQL because of this unless i'm missing something.

Can i get some pointers on this. Are my assumptions correct or am i really missing something.
Looked at the docs but no luck there.

Roel Westhoff
W4 Software & Consultancy BV
Nuth, Netherlands
http://www.ifour.eu ]]> Data Connectivity http://support.dataaccess.com/Forums/showthread.php?50452-Limitations-on-PSQL-to-MSSQL-conversion Btrieve http://support.dataaccess.com/Forums/showthread.php?50451-Btrieve&goto=newpost Mon, 29 Apr 2013 00:28:04 GMT Hello, Does anyone have a tool for connecting to Btrieve or an ODBC Driver, or knowledge of how to get one? Hello,

Does anyone have a tool for connecting to Btrieve or an ODBC Driver, or knowledge of how to get one? ]]> Data Connectivity kelly http://support.dataaccess.com/Forums/showthread.php?50451-Btrieve New features in next beta? http://support.dataaccess.com/Forums/showthread.php?50412-New-features-in-next-beta&goto=newpost Tue, 23 Apr 2013 07:37:34 GMT ---Quote--- Eddy did a session on the driver at Synergy and they are currently testing the next release which has some nifty new features like Auto...
Quote:
Eddy did a session on the driver at Synergy and they are currently testing the next release which has some nifty new features like Auto Reconnect and the SQL 2008 data types.
Will these new features be part of the next beta? I am very interested in Auto Reconnect for one of my WebApp projects and I want to verify if a time mask is part of the new VDF features when using the SQL 2008 TIME datatype. ]]> Data Connectivity Peter van Mil http://support.dataaccess.com/Forums/showthread.php?50412-New-features-in-next-beta