*************************** Question 1 ****************************

I have a webform with bound textboxes that is exibiting some odd behavior. I am hoping it will ring a bell with you perhaps.



My form works, the problem I had a few days ago went away with 1.5. The problem is this, only two 'navigate' events work.



Scenario 1:



When the form loads my initial record from the fill method is displayed, great.

When I hit my next button, the record pointer moves and the bound textbox refreshes, great.

When I hit next again, the page refreshes but I am on the same record.

I can only navigate 'prior' and 'next' and toggle between these two records.



Scenario 2:



When the form loads my initial record from the fill method is displayed, great.

When I hit my last button, the record pointer moves correctly to the last record in the table and the bound textbox refreshes, great.

I can navigate 'prior' and toggle between these two records ( the first and last record, not the last and the one prior to it)



Also my edit button correctly sets the state of the bound controls to enabled, but the call to save() refreshes the form, sets the controls to disables, but does not save my changes.



************************** Question 2 ********************************

Every time I make a change to the business object class (contained in its own project as in the WebSample) in the web project I have had to manually move the .dll to the \bin directory of the webforms project, remap, and rebuild. Is that right?



Thanks.

Keith Chisarik

Is it possible that your business object only has 2 records?  If that is the case, then you would only be able to move forward/back and first/last between those 2 records.

As for the business object not saving, if the controls are being disabled, then the business object thinks it has saved because it is setting its EditingState back to idle.  However, you might check on the return value of the Save() method and make sure it is Success and not something else.

On the assemblies, if the assembly has been added to the /bin folder as a reference, and it has been set to CopyLocal = True, then you shouldn't need to copy the DLL every time you build it, VS will take care of that for you.  However, if you notice any "funky" behavior, like changes to the business objects not being seen by the website, you can copy the DLL manually, or just add the business objects project to the same solution as the website (remember that a project can belong to more than one solution).