I am not sure. I haven't got any machine with VS2008 installed anymore, so I am not able to test this scenario at the moment. Have you tried putting a break point in the BeforeDelete and step through the source code to check it?

Hi Ivan,

Remember, I am running Visual Studio 2008 not 2010 and I made the changes to the solution and project files that you instructed me to do.  Could those be the differences between my DLL's and yours?

Sam Tenney

Well, I will stick to the "good news" part of it all.

Good to know you found a possible issue. Guess you will be fine, since you won't distribute the DLLs in a debug mode, so the users won't face the issue. I will get this on the list to have a look in a near future and see if we can think of what might be. The strange part is that I am also running the DLLs on debug mode, so I compiled the source code too.

Anyway, glad you got it going.

Hi Ivan,

Good News!  By trial and error I have found what seems to be causing the problem.  I am using Visual Studio 2008 and I like to step thru the SF framework code.  When I downloaded and ran the source code file and tried to build the various SF solutions to create the necessary *.PDB files, I was getting build errors.

On 9/4/2010 in post #28428 on this forum you provided instructions on how to modify the SF solution and project files with Notepad to allow Visual Studio 2008 to build correctly.  I followed those instructions and was successful in building the SF solutions.  Since then I have been able to step thru the framework source code with no apparent problems.  So I think the SF DLL files I am actually using are from the source code I downloaded and modified per your instructions.  I think I am not actually using the "normal" SF installation DLL files.  Both the source code file and the installation file that I downloaded were originally dated 8/31/2010.

As a test today I renamed the source code folder so that I would not be using those DLL files.  I ran my sample application and did not receive an exception.  I then downloaded the source code file fresh and ran it.  I then carefully modified the solution and project files per your instructions and then built the solutions.  I ran my sample application again and the exception returned.

I have no idea why this is happening, I just know it is happening.  I'm sure you can figure out why.

Sam Tenney

Try using Windows Explorer and searching from your C:\ by "MicroFour StrataFrame Business.dll"

Were you able to test it on a different environment?

Hi Ivan,

I am using SQL 2008 Express, but I agree with you that I don't think there could be a problem there.  In Visual Studio when I click on the StrataFrame / Version menu option, all the assemblies show version 1.7.3.1.  Where else can I look for old DLL's?

Sam Tenney

Telonics, Inc.

Hi Sam.

Thanks for the sample. I am sending you the video of my test, and you will find this strange, but it worked flawlessly here. I really wish I got the same error, so we could try and find a fix for it. There is something else going on... what SQL Server are you using, although I don't think there could be something with it. You say you are under SF 1.7.3.1, but could you please check if you don't have old SF DLLs somewhere else? If you do, get rid of them so Visual Studio won't find the wrong ones. Another test you could do would be to create a new Virtual Machine or even another computer and try on this different environment, just to check.

I have attached the test for you to have a look. If there is any other step you would like me to do with your sample, let me know and I will test over here again.

Ivan,

In the attached zip file you will find a folder named "SQL Data Folder" which contains my test database which you can ATTACH to your SQL server.  The database is named "Telonics Test Database" and the table is named "TestTable".  The solution is very basic but it does show the exception I am seeing when I run it.  There is only one record in the table.  Just try deleting it and with any luck you should see the same exception that I see.

I hope I followed your instructions correctly on how to zip up my solution etc.

I appreciate the patience you have shown with me and the time you have spent trying to help.

Sam Tenney

Telonics, Inc.

I changed only these two and it worked as advertised.

Have you tried adding a breakpoint into the BO BeforeDelete event and debug what goes on? You can also step into the framework and follow the action.

If you decide to create a sample application, just create a new application with a simple form that will reproduce the error. Once you get that done, zip the solution folder up and use the "Attach Files" link to upload it into your post.

Ivan,

It looks like I will need to learn how to send you my application before we will be able to resolve this issue.  I will work on that.

Greg McGuffey had told me that most developers are beginning to use the automatic editing mode rather than requiring the end users to click the Edit button to begin editing a record.  So I have tried to find and set all the settings required to enable automatic editing mode but apparently I had missed the ManageUIReadOnlyState property on the business object.  However even after setting it to False as you did, I am still getting the unhandled exception.  Is there a list available of all the settings necessary to enable automatic editing mode?

Sam