Over the weekend, "something" went wrong (No, no updates installed).
Trying to run DBMigration, to sync a folder of dbfs with my postgres server, i get:
ERROR [IM003] Aufgrund des Systemfehlers 1114: Eine DLL-Initialisierungsroutine ist fehlgeschlagen. (Microsoft Visual FoxPro-Treiber, C:\Windows\SysWOW64\vfpodbc.dll) konnte der angegebene Treiber nicht geladen werden.
The dll is there, as it was for many years. Tried to reinstall the dll, from msi, no error, but no change.
Tried "regsvr32.exe C:\Windows\SysWOW64\vfpodbc.dll" and got the same "Eine DLL-Initialisierungsroutine ist fehlgeschlagen".
(The strange thing is, Err 1114 is, according to the net, attributed to grafics problems on laptops. This is a normal pc without additional grafic card, nothing of its hardware got changed for years.)
Well, what now? I made an attempt using oledb, (VFPOLEDB.1) which seems to work - but not for dbs with memo. (dbf/cdx/fpt).
Someone an idea?
vfpodbc.dll / DBMigration by fish
vfpodbc.dll / DBMigration by fish
Regards
Karl
(on Win8.1/64, Xide32 2.20, X#2.20.0.3)
Karl
(on Win8.1/64, Xide32 2.20, X#2.20.0.3)
Re: vfpodbc.dll / DBMigration by fish
Hi Karl,
AFAIK DBMigration is delivered as single executable file - that means that all needed DLLs are integrated into the executable.
Some systems does not like that - on a customers PC this type of executables is completely blocked by his (enterprise) antivirus software.
Wolfgang
AFAIK DBMigration is delivered as single executable file - that means that all needed DLLs are integrated into the executable.
Some systems does not like that - on a customers PC this type of executables is completely blocked by his (enterprise) antivirus software.
Wolfgang
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Re: vfpodbc.dll / DBMigration by fish
Hi Wolfgang,
thx - but i use DBMigration now for almost 10 years, never had that problem. Been using the actual version for months, also my "Windows updates" list does not show any action for the last weeks, so i'm lost, why all of a sudden that problem appears.
If i understand the error correctly, the fail in itself seems not to be with Vfpodbc.dll, but in the "DLL-Initialisierungsroutine", whatever that may be.
Any idea, why the Vfpoledb.dll doesn't digest memo fields? I'd suspect that there may be some version bit in the dbf header, which it doesn't like. Is there a difference between Foxpro and Vo in that regard?
thx - but i use DBMigration now for almost 10 years, never had that problem. Been using the actual version for months, also my "Windows updates" list does not show any action for the last weeks, so i'm lost, why all of a sudden that problem appears.
If i understand the error correctly, the fail in itself seems not to be with Vfpodbc.dll, but in the "DLL-Initialisierungsroutine", whatever that may be.
Any idea, why the Vfpoledb.dll doesn't digest memo fields? I'd suspect that there may be some version bit in the dbf header, which it doesn't like. Is there a difference between Foxpro and Vo in that regard?
Regards
Karl
(on Win8.1/64, Xide32 2.20, X#2.20.0.3)
Karl
(on Win8.1/64, Xide32 2.20, X#2.20.0.3)
-
mainhatten
- Posts: 211
- Joined: Wed Oct 09, 2019 6:51 pm
Re: vfpodbc.dll / DBMigration by fish
Hi Karl,
From Vfp POV VfpODBC is old - not venerable, but out of time, as it only supports up to vfp6, no Autoincrement, no index BINARY and so on. If it works for your dbf structure, fine. Then I'd reinstall it (several ways listed on VfpX, with files for runtimes or standalone).
Differences in Memo: AFAIR the width of the pointer into FPT changed from 10 to 4 bytes, only Vfp had 4-bit-integer field type. Hard to believe MS deleted ability to read 16 bit style memo fields from OleDB, but worth checking. Another possibility: in Vfp some commands need special keyword to work with memo fields right off the bat, as this was a file-/networkaccess optimization not irrelevant with slow PATA/IDE HD or Token Ring or Hub-braked 10MBit cables. Check on Connection Strings if similar option needs to be flagged. I doubt there is a blocksize setting OleDB refuses to work with without clear error output.
Vfp Help files are on VfpX as well, but AFAIR OleDB not defined in depth there. Grab a runtime, runtime command window and create a cursoradapter with ADO (uses OLEDB) or ODBC and test from there. Search for Doug Hennigs PDFs on Cursoradapter if that is a dark horse for you, he even has demo code for all access tech easy to run as prg.
HTH
thomas
From Vfp POV VfpODBC is old - not venerable, but out of time, as it only supports up to vfp6, no Autoincrement, no index BINARY and so on. If it works for your dbf structure, fine. Then I'd reinstall it (several ways listed on VfpX, with files for runtimes or standalone).
Differences in Memo: AFAIR the width of the pointer into FPT changed from 10 to 4 bytes, only Vfp had 4-bit-integer field type. Hard to believe MS deleted ability to read 16 bit style memo fields from OleDB, but worth checking. Another possibility: in Vfp some commands need special keyword to work with memo fields right off the bat, as this was a file-/networkaccess optimization not irrelevant with slow PATA/IDE HD or Token Ring or Hub-braked 10MBit cables. Check on Connection Strings if similar option needs to be flagged. I doubt there is a blocksize setting OleDB refuses to work with without clear error output.
Vfp Help files are on VfpX as well, but AFAIR OleDB not defined in depth there. Grab a runtime, runtime command window and create a cursoradapter with ADO (uses OLEDB) or ODBC and test from there. Search for Doug Hennigs PDFs on Cursoradapter if that is a dark horse for you, he even has demo code for all access tech easy to run as prg.
HTH
thomas