MainDemo sample app, Web, XAF 8.1.6, New Contact, enter key => Error 1007

Tags:

Adam Leffert 07.18.2008

- Hitting the enter key in a new contact record in MainDemo web app crashes with an error 1007.
  Steps to Reproduce:
  I started with a clean copy of the MainDemo app.
  Set startup to Web app.
  Compiled in VS2008.
  New SQL Server db.
  Log in.
  Click "Contact" in the navigation bar.
  Click "New".
  First name: John
  Last name: Doe
  Hit the enter key => crash
  I started with a clean copy of the MainDemo app.
  Set startup to Web app.
  Compiled in VS2008.
  New SQL Server db.
  Log in.
  Click "Contact" in the navigation bar.
  Click "New".
  First name: John
  Last name: Doe
  Hit the enter key => crash
  Actual Results:
  The error occured
       Type: InvalidOperationException
       Message: An error with number 1007 has occurred.
  Error message: Unable to execute disabled or inactive action. Disable reasons: Can move to previous, inactive reasons:
       Data: 0 entries
       Stack trace:
     at DevExpress.ExpressApp.Actions.ActionBase.ExecuteCore(Delegate handler, ActionBaseEventArgs eventArgs)
     at DevExpress.ExpressApp.Actions.SimpleAction.DoExecute()
     at DevExpress.ExpressApp.Web.Templates.ActionContainers.SimpleActionItem.Button_Click(Object sender, EventArgs e)
     at DevExpress.Web.ASPxEditors.ASPxButton.OnClick(EventArgs e)
     at DevExpress.Web.ASPxEditors.ASPxButton.RaisePostBackEvent(String eventArgument)
     at DevExpress.Web.ASPxClasses.ASPxWebControl.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
     at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
     at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
       InnerException is null
  Expected Results:
  Record gets saved.
  I know that testing Web apps is tricky, but from what I see of this error, it's not dependent on the specifics of the Web UI to the point where it would take screen-scraping software to test it. I believe a call to the correct method at the correct time would produce the error.
  Also, I have no business connection with the company, but there is a software company that sells an inexpensive Web macro (scripting) program that is easy to use. I won't mention their name here out of respect for your site, but you can email me if you'd like their contact info. I've used the program for a few years successfully. You record a macro and it plays back, opening the web site and running it. It can also be scripted with .Net to check the results automatically.
  I also remember reading that DevExpress is doing some automated testing in connection with CodeCentral.
  Thanks very much in advance for fixing this problem.
  Best,
  Adam

Dennis (DevExpress Support) 07.21.2008

Hi Adam,

Thank you for the report and your comments. We appreciate it greatly.
This is the default behavior of the browser. After the Enter key is pressed it searches for the first button on a page and then "presses" it. In this instance, the button's XAF action is executed. But, this action is disabled and the error you received occurs as expected.
You can see this default behavior by creating and testing a non-XAF application that will contain a simple page with a button.

Thanks,
Dennis

Adam Leffert 07.21.2008

I love your products, and your support is usually outstanding, but this is a non-answer.

All you've done is describe the bug in different words.

Hitting the Enter key to save and close a record is one of the most basic actions a Web user can take. It's not as if the user is doing some unusual thing that I can tell him not to do.

I can't tell my users not to hit the Enter key. I need to demo my work in XAF and later, I need to deliver the application to the users.

If I understand your response correctly, the crash is not caused by misuse of XAF, so I don't yet know how to use XAF so that it doesn't crash when users hit Enter.

Please tell me how to use XAF to create app's that don't crash when users hit the Enter key.

I am working very hard on an app based on XAF and look forward to creating many more. I've bought one full subscription, convinced one person who will also definitely buy one, and will keep going from there.

Thanks in advance,

Adam

Dennis (DevExpress Support) 07.22.2008

Hi Adam,

Thank you for your feedback.
We see the problem but this is not a problem of XAF. This is a default behavior of browsers for other ASP.NET applications as well.
>>
Hitting the Enter key to save and close a record is one of the most basic actions a Web user can take.
<<
We consider that hitting Enter could take place if you want to activate some focused control on a page, for instance a button to press it, etc. There are a lot of other examples. But, this is not the matter.
I wanted to say that hitting the Enter key always and everywhere doesn't make sense, especially if you click on a page layout (how this error occurs).

>>
Please tell me how to use XAF to create app's that don't crash when users hit the Enter key.
<<
The only way is writing a custom script for the page that will catch the Enter key, perhaps against of some conditions. We have no ready sample for this, because this is not a problem with our product. You need to create this script yourself as well as to determine the conditions of when to allow or when to prevent the key press.

Please do not hesitate to contact us in case of any problem. We are always happy to help you.

Thanks,
Dennis

You must log in or register to leave an answer

Is your intention to post an answer to your own question?

If so, then proceed.
If you simply wanted to post additional information, ask for further clarification, or to just say "Thanks!", please click Leave a Comment.
If you wish to edit your original question, please use the Edit button in the Toolbox at the top right corner of that entry.

MainDemo sample app, Web, XAF 8.1.6, New Contact, enter key => Error 1007

Imported from SC 1.0

Fixed

Fixed in

MainDemo sample app, Web, XAF 8.1.6, New Contact, enter key => Error 1007

Imported from SC 1.0

Fixed

Fixed in

Related Articles