Diese Seite mit anderen teilen ...

Informationen zum Thema:
WinDev Forum
Beiträge im Thema:
Erster Beitrag:
vor 1 Jahr, 6 Monaten
Letzter Beitrag:
vor 1 Jahr, 6 Monaten
Beteiligte Autoren:
GuenterP, Piet van Zanten, Ola, Harry W, Fabrice Harari

Import HFSQL Classic files => HF C/S

Startbeitrag von GuenterP am 16.02.2017 18:11


here are some frustrating observations when importing HF Classic files into HF Client/Server using the HF Control Center v21

1 - in the analysis, one can define the logical name of a file and the name on disk. HF Control Center will only detect files where logical name = file name on disk

2 - HF Control Center does not recognize any other file extensions than .FIC !!! We're using .DAT because "FIC" sounds like a bad word in German (means the same as "fuck" in English).

3 - After changing all of the file names and all of the file extensions manually, it recognizes the files and seemingly does import them, i.e. it takes a lot of time to import and ends with a message box saying that it's finished. However, while all of the files are shown in the database not a single record appears in any of the files. Trying to repair all of those empty files ends with a decent crash.

Similar experience with HF Control Center v22 with the nice add-on that it's crashing already at the end of the import without telling me that the import could be done successfully .... no records in the database.

Same goes with not defining the analysis file (.wdd) which is possible and of course does not transfer the integrity rules (links).


Hi Guenter,

I don't know about the logical/physical names problem (I'm always using the same ones), and I'm pretty sure that you already know the following information, but justin case you don't :
- you can just copy the HF classic files into the BDD (C/S) directory
- THEN you access the files in HF C/S from your program, and the DB is created in the control center with the files already filled
- or you can of course stop the control center and copy/overwrite the files

it's much faster than the import.

Best regards

von Fabrice Harari - am 16.02.2017 18:31
Hi Fabrice,

of course, I always did so but I'm not 100% sure that all of the mechanisms within the HFSQL C/S Server will run just fine right from the start after doing the copy operation. Yes, re-indexing should fix that problem. Does it? One of the questions is why they put such a defective function into the HF CC at all and did not resort to a simple copying routine? However, I'm not amused and sent an error report to PC Soft.

von GuenterP - am 16.02.2017 21:04
1 - in the analysis, one can define the logical name of a file and the name on disk. HF Control Center will only detect files where logical name = file name on disk

You can use HChangeName() to give the file another name.

von Harry W - am 16.02.2017 22:51

of course, I can write a small program for the transfer of data into the HF C/S database myself. If I want to change names etc. this can be done by code. But I don't want to since we are offered a utility. Just as a reminder: this is not a gift, we've paid for it. Here we have a not-working utility integrated into the HFSQL Control Center, probably since years. I wouldn't let any of our programmers get away with such a $%&/* piece of software.

von GuenterP - am 17.02.2017 06:28
Hi Guenter,

It seems you are little by little learning to use the correct adjectives to describe the (beep) that PCSoft spits out:-)

Best regards

von Ola - am 17.02.2017 09:52
Hi Fabrice,

copying the files to the database directory alone is not enough. They have to be synchronized with the analysis - otherwise the links / integrity control would be missing. I tried to use the Synchronization from the HF CC v21 and got the message "DLL missing". It didn't say which DLL. So, you have to have to start the project with WINDEV, open the analysis and synchronize the files in the directory. Not very user friendly.

von GuenterP - am 17.02.2017 21:01
Hi Guenter,

Somewhere in the previous century when there was no client-server yet, I first started using hyperfile.
I used .dat for the file extension because I was used to it in Btrieve.
Soon I found out the hard way that it was a no go because of all the trouble it caused.
So I decided to go with the flow and since the Dutch don't have this dirty word problem there was no real reason to not use .fic.

I guess that's what in the end we all do using WX products: find a workaround and leave the half baked features unused, lurking to trap new ignorant victims. Don't get me wrong, I like WX, but it has been said before on this forum, the lack of a decent bug list is a shame.

Kind regards,

von Piet van Zanten - am 18.02.2017 09:42
Zur Information:
MySnip.de hat keinen Einfluss auf die Inhalte der Beiträge. Bitte kontaktieren Sie den Administrator des Forums bei Problemen oder Löschforderungen über die Kontaktseite.
Falls die Kontaktaufnahme mit dem Administrator des Forums fehlschlägt, kontaktieren Sie uns bitte über die in unserem Impressum angegebenen Daten.