Could you post the source code for your .aspx.vb and .aspx pages that are causing the problem as well as the code for your applicationbasepage2.vb file.  If this is a production site, or you are uncomfortable posting it here, then you can email it to me.  Thanks.

I'm sending you an e-mail.

Thank you.

Ben, you give great support!

..ßen

I don't know if this can help, but if I add the business object to the ApplicationBasePage.cs too, and continue to reference the ApplicationBasePage2.cs , I get no error and I am able to select a field in BindingField property.

I am stuck with this.

Thanks for sending the source code.  I was able to reproduce and fix the error that you received.  The fixes will be included in the next release here in the coming 2 or so weeks.  In the meantime, you can workaround the problem by leaving the definitions in your main ApplicationBasePage.cs file.  I would post the updated DLLs, but several other things have changed, and I don't want to cause you more headaches by sending you DLLs that will break what you're working on.

Thank you.

I was pulling my hairs..

Now I can wait  and let them grow again   

Hi Hugo.

Ask Ben for some of his. He's got plenty to share...

Did I mention that I shaved my head last week?  It's not a pretty shaved head, but...

just kidding...

FYI.

A developer at my company also received this error while attempting to build a web project using strataframe objects:

Invalid access to memory location. (Exception from HRESULT: 0x800703E6) in web.config file in the following line:
<add assembly="Microsoft.SqlServer.Replication, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845DCD8080CC91"/>

It was resolved by re-registering the following 2 dlls:

regsvr32.exe msxml3.xml
regsvr32.exe msxml6.xml

Good luck,

Jason Stevenson