Expert can not load a SIB into a form

Jean-Paul Brassard · Post by **Jean-Paul Brassard** » Fri Aug 27, 2010 10:34 pm

Strange, very strange...

Today, my collegue tried to make a Load command to push new translations from a SIB into a Delphi-7 form (DFM).

The Load does not succeed, no feedback, no error message, the DFM was just not loaded???

Few seconds after the load, Delphi crashed with a popup windows asking to send the error to Microsoft.

He tried a few times to uninstall TsiLang and reinstall it with no success, always the same problem and crash.

He finally install the full source version of TsiLang and then everything works fine !?!?!?!?

Does anyone has already seen this strange behavior?

By the way, the SIB contains 2,400 records from which almost all of them differs from the contents of the form. These new values in the SIB are because I filled in the third language, last week. So the Load command has a great lot of job to do...

Post by **isiticov** » Sun Aug 29, 2010 8:58 am

Hi Jean-Paul,

May be the Delphi 7 version on that PC doesn't have all updates and service packs installed? This may be a reason of strange behavior on compiled packages.

Jean-Paul Brassard · Post by **Jean-Paul Brassard** » Tue Sep 07, 2010 4:36 pm

isiticov wrote:Hi Jean-Paul,
May be the Delphi 7 version on that PC doesn't have all updates and service packs installed? This may be a reason of strange behavior on compiled packages.

This could not be the case since the error does not show on two other PC which have been recently installed with the same ghost.

Moreover, this does not explain why the problem is resolved as soon as the TsiLang binary version is replaced by the full source !!! ???

Post by **isiticov** » Wed Sep 08, 2010 2:56 am

Jean-Paul Brassard wrote:Moreover, this does not explain why the problem is resolved as soon as the TsiLang binary version is replaced by the full source !!! ???

Especially this explains that there are differences in updates packs installed on 2 PCs.

Because the code is proper and the strange behavior is caused only by difference in IDEs and binary codes for package. Once you've installed full source and re-built the packages under target IDE they became absolutle compatible with such IDE and the strange behavior dissapear.