[ilink32 Error] Error: Unresolved external 'InternetOpenUrlW' referenced from ...\TMSVCLUIPACKPKGDXE11.LIB|AdvUtils
[ilink32 Error] Error: Unresolved external 'HttpQueryInfoW' referenced from ...TMSVCLUIPACKPKGDXE11.LIB|AdvUtils
[ilink32 Error] Error: Unresolved external 'InternetReadFile' referenced from ...\TMSVCLUIPACKPKGDXE11.LIB|AdvUtils
[ilink32 Error] Error: Unresolved external 'InternetCloseHandle' referenced from ...TMSVCLUIPACKPKGDXE11.LIB|AdvUtils
Can it be there are still old advutils.hpp files on your system?
Search your hard disk and delete such old version files.
#include "AdvObj.hpp"
#include "AdvUtil.hpp"
#include "BaseGrid.hpp"
Can you verify that
(if it is the latest version, it should have this line)
When you use TAdvTreeView , AdvUtils.hpp should be (indirectly at least) used.
Apparently not, I can build a project with a TAdvTreeView even after renaming AdvUtils.hpp
That is an indication the compiler uses another AdvUtils.hpp as the unit ADVUTILS.PAS is used from TAdvTreeView.
I checked this and version number on website and in source code are out of sync
The version v1.1.4.2 is what is in the latest TMS VCL UI Pack, so you have the latest version installed.
We'll look to sync these version numbers again, sorry for the confusion.
I have the same issue. I'm upgrading from Tokyo 10.2.3 to Rio 10.3.2. This is the first time I'm installing the new UI Components. If I just ignore the error I get a error, "Error creating form, stream read error" and can't view the form. I'm installing the latest version of the UI component pack, downloaded yesterday. This is a major issue for me.
Hi Bruno - yes I've read the FAQ and I see you've made some fundamental changes to the AdvTreeView component. But how do I fix it? What's the workaround? At the moment I cannot view my form after I get the stream read error.
Hi Steve,
Bruno,
These events have not changed.
My error - I added a TAdvCheckTreeView, instead of TAdvCheckedTreeView
Hi everyone!
This solution worked for me! I had been getting this error after opening forms with TAdvTreeViews on them (or descendants), and ignoring the Delphi IDE errors:
Error creating form: No mapping for the Unicode character exists in the target multi-byte code page.
So, like Otstavnov said, I opened those particular .dfm's, searched for "Version =", removed those lines, saved them, and they were able to open in Delphi (although they still had the initial errors and warnings with component property values).