I have an application written in Delphi 5 which uses a Paradox ".db" database. My application makes a call to a set of scripts written in Perl and uses ODBC to access the DB tables to collect data and generate XML files.
Everything works fine on my PC (Win 7, 64 bits), but not on a 32-bit Win 7 PC. The Perl script fails and I get the following error:
-1305[Pilote ODBC Paradox] le moteur de base de données microsoft Jet n'a pas pu
trouvé l'objet xxxx.
When I close the Delphi application and run the scripts manually it works fine.
For those who may faces the problem, i have got the solution. i changed the configuration of BDE as follow: SHAREDMEMSIZE = 1024. MAXBUFFSIZE = 2048. It is recomanded that MAXBUFFSIZE = 2* SHAREDMEMSIZE. And to allow running multiple Applications using the BDE to set the SHAREDMEMSIZE less than 2048.
Related
I develop an application using VB6 and ODBC that fetch data from PostgreSQL function.
I used the function "F0006" to get information about item code, name, etc.
So far, my application runs smoothly on the current PC ( Windows 7 SP1 ). Because of the end of the support of Windows 7, we buy a new PC to replace the current that has Windows 10 installed.
We set up the same ODBC connection based on the currently running one and Connection success. But when we try to test our application to fetch the data, it seems can't find the function "F0006" and throw an unknown function message in the New PC ( Windows 10 ).
FYI, PostgreSQL is managed by others, and we don't have Admin DB access to it, and Active Directory is used in our network.
But if we try the same application in the current PC ( Windows 7 ) and other PC that using Windows 10 that has not configured to network AD, the application can get fetch data from the function.
Where could be the source of the problem?
Thanks
I have installed Firebird 3.0.2 (x64) and IBExpert 2018.12.15.1.
I'm trying to create a Firebird DB on IBExpert but everytime getting this error:
Unsuccessful execution caused by system error that does not preclude successful execution of subsequent statements.
Error loading plugin Engine12.
Module C:\Program Files\Firebird\Firebird_Server\plugins/Engine12 exists but can not be loaded.*
My configuration:
Server/Protocol
Local, XNet (FB3)
Database
C:\Data\Example.fdb
Connection string
xnet://C:\Data\Example.fdb
Client Library File
C:\Program Files\Firebird\Firebird_Server\WOW64\fbclient.dll
Username
SYSDBA
Password
masterkey
Page size
126384
SQL Dialect 3
How to solve this problem?
This happens to me when I select the firebird fbclient dll from the following location
C:\Program Files\Firebird\Firebird_3_0\WOW64\fbclient.dll
However if I instead (against all sanity and reason) chose what I think ought to be a 64 bit dll, from c:\windows\system32, it works.
ie, client choice:
c:\windows\system32
Now it might seem logical to some readers that system32 could contain a 32 bit dll, but actually almost every dll in there, and probably EVERY dll in there SHOULD be 64 bit, on windows 64 bit systems. However I am guessing that whatever is in there must be a 32 bit fbclient.dll in the main windows 10 system directory.
Microsoft made a now ancient but at the time, kind of odd decision that c:\windows\system32 will be full of 64 bit stuff on Windows XP 64 bit, and has kept it that way. It appears to me there's something wrong with Firebird 3.0.4's installer team's decisions.
I need to write to an application log on a remote Window 7 computer. When my PC was running Windows 7, I could do so using a Write-Entry cmdlet, eventcreate, WriteEvent API, or LogEvent in VBS. Since upgrading my PC to Windows 10 (v1511), this no longer works failing with an error "The procedure number is out of range". I can write to an application log on a remote Window 10 machine, but the problem is with the remote (not firewalled) Window 7 PC. How can this problem be solved?
I use
JetGetDatabaseFileInfo(db_name, &db_page_size, sizeof(db_page_size),JET_DbInfoPageSize);
JetSetSystemParameter(NULL, NULL, JET_paramDatabasePageSize, db_page_size, NULL);
to set the same page size of as a database have.
There is a database with page size == 32768. On windows 7 this code works perfectly. On Windows Vista JetSetSystemParameter returns JET_errInvalidParameter. Is there any way to open a database with page size of over 8192 on Windows Vista?
No. 32k pages were added in Windows 7.
Even if the database had 8k pages, there are other Windows 7 changes that would make the Vista esent.dll unable to open the Win7-based database file.
If it's just for your own use, you can copy the Win7 esent.dll to a Vista machine. But I don't believe that it's permissible to redistribute esent.dll with your program.
-martin
I have a client with FileMaker Pro 11 Advanced.
I need to be able to connect to the filemaker database via SQL. I am using MS SQL Server 2008 R2, or Server 2012 can be used.
These are the steps I have tried
0) Turned on ODBC/JDBC sharing in File -> Sharing on FileMaker Pro 11 Advanced for "All Users"
1) installed the FileMaker OBDC driver included on the filemaker disc
2) odbcad32.exe in C:\Windows\SysWOW64 and added a new filemaker System DSN and directed it to the filemaker database.
3) Attempted to add a linked server to SQL using Provider Microsoft OLE DB Provider for OBDC Drivers and the System DSN name i created for Data Source. I left all other fields blank.
I get this error:
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "FILEMAKER2".
OLE DB provider "MSDASQL" for linked server "FILEMAKER2" returned message "[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application". (Microsoft SQL Server, Error: 7303)
FILEMAKER2 is the what i called the System DSN.
What am I doing wrong/What do I need to correct in order to connect to filemaker with SQL?
Is there a connection string to put in for Provider String?
I have the same mismatch error trying to do a test connect with access.
Thank you for any help.
The error you're getting is because of the driver installed is a 32bit driver propably on a 64bit system.
Look in the downloads of FM for the correct xbit driver.
I've connected to FM using ODBC from PHP apps to do basic inserts, updates, deletes of data. I haven't worked with it like you're attempting to do, though, and like #ted said, FM really wasn't built as a SQL platform.
Their answer to this was to go the other way around. You can setup External SQL sources within FileMaker, and bind your SQL database to FM so that those tables show up in FM the same as regular FM tables. These tables can then be used within FM scripts accordingly, so you could setup any data sync steps necessary there. You could create scripts to move data from FM layouts into the SQL DB layouts at given intervals throughout the day, for example.
Hope that helps.
FileMaker 11 only comes with a 32 bit ODBC driver. The error you got happens when you use a 32 bit driver with the 64 bit ODBC admin utility. Set up your DSN using the 32 bit utility, found here:
C:\Windows\SysWOW64\odbcad32.exe
...and it will work fine.