Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I give this question a try. The flow you mention will obstruct the pages normal function, which you of course already have in mind. Though, i would say it can be dangerous (against the function you expect) and contraproductive. Based on what I can see from your question, I would definitively remove Page2 and Page3 and keep all logic in same and single page. </p> <p>I would also be happy to hear what you are trying to avoid, with this? Is it double posts? Like a double-post of a content in a shopping cart? Partial / uncomplete inserts of data input? With the described way to affect back-buttons, you may come around one problem but rise another. A big range of browsers that can act completely different on such work-arounds. </p> <p>I see two good options,</p> <p>UserControl,<br> Create three UserControls which every each of them have each page specific logic. You can programmatically load them into the page. I.e. on <code>bnButton_Click</code> Event. Usercontrols are loaded with <code>LoadControl("PathToAscxFileOnDisk.ascx")</code>. </p> <p>Panels,<br> I would also think about three <code>&lt;asp:PlaceHolder&gt;&lt;/asp:PlaceHolder&gt;</code> or perhaps better <code>&lt;asp:Panel&gt;&lt;/asp:Panel&gt;</code> to put all logic into. </p> <p>In this case you are completely free from the postback issues and can focus on moving your functions into business logic and have use the Code-File to control the flow on show/hide and populate the controls in/out from the panels/usercontrols. You can probably also control the postback / click-URL &amp; push-enter-key.</p> <p>And you mentioned Ajax,<br> Ajax is absolutely there to make your page stateless (which means you can work without cache, sessions, viewstate and so on. Though, the problem lies in the users possibility to navigate between pages. I would think even Ajax is of less help, while you keep the three-pages-solution.</p> <p>I would personally say it is a simple task to move the aspx files into each ascx and create a aspx as a master-container. With that option you even avoid duplicate namings (like if you copy / paste the code into panels) and trouble with Page_Load flow/logic.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to implement PRG pattern properly in asp.net webforms
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USIndependent
    1. USIndependent
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COthanks for the input. I am not afraid of double posts since I have confirmed pressing back on Page3 and pressing the OK on the resubmit post popup does indeed take you back to Page1 (for FF at least). I just didn't want this resubmit popup to be displayed. Interesting solution you propose, I might look into this soon.
      singulars
      1. PO
      1. USLuke Hutton
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload