Runtime package, vcl100.bpl, Access violation
Henrik Andersson
I have a runtime package, that is called from my main application. It
used to work. Suddenly I get this, after re-compiling:
Access violation at address 52006167 in module 'vcl100.bpl'. Read of
address 00000010.
I have not changed the code, and I can't see what is changed in my
development environment.
The BPL that is generated from my package has the same size but
different content to the previous compile...
Any ideas?
BDS 2006, update 2
--
Henrik
Peter Below (TeamB)
> Hi
>
> I have a runtime package, that is called from my main application. It
> used to work. Suddenly I get this, after re-compiling:
>
> Access violation at address 52006167 in module 'vcl100.bpl'. Read of
> address 00000010.
That is the typical signature of accessing a field through an object
reference that happens to be nil. Do you get this when running the
rebuild application or during the compilation? If the former, do you
get it before the main forms shows up or later (that is: can you get
through the creation sequence and up to Application.Run without error)?
> I have not changed the code, and I can't see what is changed in my
> development environment.
It may be an accidential property change on a form, e.g. a change to
OldCreateOrder. I don't think the cause could be in the package itself
if you are *really really* sure that the source for that was not
changed.
--
Peter Below (TeamB)
Don't be a vampire (http://slash7.com/pages/vampires),
use the newsgroup archives :
http://www.tamaracka.com/search.htm
http://groups.google.com
Henrik Andersson
>
> That is the typical signature of accessing a field through an object
> reference that happens to be nil. Do you get this when running the
> rebuild application or during the compilation?
When running
If the former, do you
> get it before the main forms shows up or later (that is: can you get
> through the creation sequence and up to Application.Run without error)?
Well, before. But I only use forms in one unit in the package. And this
error occurs in units that don't use forms.
The main client application runs fine though.
>
>> I have not changed the code, and I can't see what is changed in my
>> development environment.
>
> It may be an accidential property change on a form, e.g. a change to
> OldCreateOrder. I don't think the cause could be in the package itself
> if you are *really really* sure that the source for that was not
> changed.
>
My colleague could compile and run the code, and I can run his build.
Now I did a clean install of Delphi 2006 Enterprise, ran update 2 and
hotfixes. Though it did not help.
Peter Below (TeamB)
> If the former, do you
> > get it before the main forms shows up or later (that is: can you get
> > through the creation sequence and up to Application.Run without
> > error)?
>
>
> Well, before. But I only use forms in one unit in the package. And
> this error occurs in units that don't use forms.
>
> The main client application runs fine though.
Do you mean the application seems to run OK if you OK the error dialog?
You could try to debug this: set a breakpoint on the first
Application.CreateForm line in your application, run to it. Does the
error appear before you reach the breakpoint? If not, F8 over each
statement up to Application.Run. If the error appears during one of
these jumps you at least know which form is responsible. Is it a
package-based one? Or does it call some code from the package?
Check the versions of the standard packages like vcl100.bpl on your
system against those on your colleagues system. Search your disk for
vcl100.bpl in particular, there should be only one copy of it around,
in the system32 folder. Also search for copies of the package in
question, make sure you only have one copy of the BPL around.
Henrik Andersson
thirdparty component for Excelexport (TscExcelExport)
with scExcelExport do
begin
Name := 'scExcelExport';
DataPipe := dpDataSet;
Dataset := query;
StyleColumnWidth := cwAutoFit;
ColumnWidth := 0;
FontHeader.Size := 12;
BeginRowTitles := 1;
BeginRowData := 2;
ExcelVisible := False;
end;
Oh, well. I'm closer now.
Thanks for the help.