Data Access Worldwide Forums - Database Connectivity

Impossible to migrate server due to connectivity issues

JeffKimmel — Fri, 05 Jun 2026 17:42:28 GMT

All,

In a very frustrating migration attempt I am unable to successfully connect to my SQL server. I bailed on trying to get the 19.0 version working so I tried updating to 23. I'm getting conneciton errors and when I try to look at database explorer I get the following message:

c:\vdf23.0\bin64\dbexplor.exe
Cannot open cache file for write c:\WebApps\vdf rfidentity\Data\Company.x64.cch , Source = MSSQLDRV.Open
Error: 13001

That file exists on my drive so what the heck is going on? I am an admin & have full rights to everything (at least I should) so what is stopping this from working? I'm have little to no confidence that as the product gets older, it's getting less stable. How can accessing the data be this hard? Sorry for the whining but I've been at this for almost 2 weeks and I can't even get the simplest app to work. As an FYI, I have another app in 23 that is working and can access the database so I'm at a complete loss (again).

Thanks,

Jeff

GoldStar software - access Pervasive tables from MS SSMS

DaveR — Wed, 03 Jun 2026 15:29:00 GMT

If you are still running that old warhorse Btrieve/PervasiveSQL/Actian/ActianZen you probably already know about Goldstar, but I stumbled over the following on their website white papers page yesterday. If I knew this I had forgotten it...

Microsoft Word - SettingUpLinkedServerFromSSMSv19.doc

the whole set of papers are at:

White Papers for Accessing PSQL Data | Goldstar Software

Relationships

Tom — Fri, 29 May 2026 17:06:03 GMT

Hi,

We are doing an upgrade from MS SQL Express 2014 to MS SQL Express 2025 in a test workspace. When the restoring the data from a 2014 backup to 2025 the database relationships are missing.

Also restored 2014 to 2022 and the relationships are present, then restored 2022 to 2025 and the relationships did not restore.
Not sure what we are missing?

Thanks,
Tom

SQL Image Field to .Jpg

Boris — Thu, 28 May 2026 21:15:42 GMT

DF 25.0

Code:

Send SQLExecDirect of hStmt (SFormat("Select PROVEEDORES.IMAGENLOGO1 from PROVEEDORES WHERE CODIGO='%1'",PROVEEDORES.CODIGO))





                                    Get SQLFetch of hstmt to iResult

                                    If (iResult <> 0) Begin

                                        Get SQLColumnType of hStmt 1 to iColumnType

                                        

                                        If ((iColumnType = SQL_BINARY) or (iColumnType = SQL_VARBINARY) or (iColumnType = SQL_LONGVARBINARY) ) Begin

                                            Repeat

                                                Move 100 to iChunkSize

                                                Get SQLGetDataToUChar of hstmt 1 100 to uaChunk

                                                

                                                If (SQLResult = 1) Begin 

                                                    Move (AppendArray(ucaImageBuffer,uaChunk)) to ucaImageBuffer

                                                End

                                            Until (SQLResult <> 1)

                                        End

End

When I check the column type for this field, I get 1=Char. The field in sql is Image and in DataFlex is Binary, so, for some reasong I get this value wrong.

Am I doing something wrong?

I need to extract images from the DB and save it as .jpg's

Thanks in Advanced.

SQL connection error

JeffKimmel — Thu, 28 May 2026 16:25:56 GMT

All,

I'm migrating servers and I'm getting a strange error. On VDF 19.0 I'm trying to open a file in the studio, however I'm getting the error:

'Can't open table Minimum client version not found. \nMinimum required database client version = 10 (SQL Server Native Client 10.0),\n(highest) installed database client version = 8 (SQL Server)\n , Source = MSSQLDRV.Login'

Now I've never seen this error but if I copy an older version of MSSQLDrv.dll it then works. I don't think that's the correct path to go down but my question is what should I check for? This is a brand new machine with the latest and greatest SQL so I can't imagine it's not the most up to date but I'm lost as to where to start. Any advice and/or tips appreciated.

Thanks,

Jeff

OEM to ANSI wizard cuts off long fields

Pieter van Dieren — Fri, 15 May 2026 13:51:33 GMT

EDIT: It wasn't a limitation of the wizard: the INT file contained a restriction. So forget I asked. :-)

Hi all,
I want to migrate an SQL database from OEM to ANSI/Unicode.
For this, I am using the wizard in the Database Builder.
However, this wizard has a 16K limit. Fields containing more text are truncated at 16K.
This affects quite a large number of fields. Creating scripts to correct these text fields after running the wizard would be a pita.

I'm now figuring out if I can do this in SQL instead and this works just as well.

Any tips?