I have a program which requires the user to key-in data. My database is working fine though; I can view all records made.
However, the past record is being displayed at the bottom of my add button:
my question is, is there any way to change so that when I clicked "Add", it goes to another page and load the data instead?
Related
Im experiencing a problem where when I try to open a page of an item in a table, the first record in the datasource always opens first.
My setup. I have a page "SystemDetails" with the datasource "System", and a table within that page with a datasource "System:ActionItems"(relation). Within the table, I have a button for each row that when clicked, shows a different page "ActionItemDetails".
An example of my problem. Say I click in the table an item with Id #3, the page "ActionItemDetails" shows, but the page's content loads with item Id #1. However, when I go back to the "System" page and retry clicking Id #3, it loads Id #3 as desired, and I am able to successfully open every item successfully.
This problem seems to only happen on the first time I open the "ActionItemDetails".
I thought this should be able to work natively in appmaker without any code, but I have also tried using selectKey and selectIndex in the edit button with no luck.
A side note. I also noticed that when the page "ActionItemDetails" first loads, there is only one item loaded when I console.dir(), so think the problem seems to be coming from not loading all the items.
Using the Details Master pattern. When the form initially loads it shows a grid. When clicking on the grid the details are displayed, and is working perfectly fine. The issue with this design pattern is the first record is always loaded so when I look at the cursor the first record is showing.
I'm populating a two list view controls through code (one is available items and the second is selected with buttons to move the items back and forth between the controls) and my issue is when I press "New" the detail page is displayed but the list view is populated for the first record selected. I need a way to know when "New" is pressed I can clear out the list view selected control and just populate the available values.
I ended going a different direction and creating my own "New" button that calls a menu item to call a new form as a popup similar to how the form when entering a new customer works. Then I turned off the "New" button and now my code works fine without have to deal with the one screen containing both forms logic.
So I have a webpage, that has about 30 - 40 different controls (mainly radio buttons and checkboxes) that users can select as part of an IT request for new equipment. I am storing all of this data in a dictionary, that I then pass onto a database.
Also on this page is a button called 'Next', that when clicked goes to a different page that displays a crystal report in the browser of what they chose on the previous page. This allows them print the report, or save it or submit onto HR.
On the report page is the "previous" button, that when clicked takes them back to the page where they selected all the different options.
My issue is: When I click the previous button, the selections of the different controls is lost. So I was thinking about adding my dictionary to a session variable, so that upon a 'Previous' click, I could retain that data and set the controls to what they had chosen.
Is this a good idea? Why or why not?
Is there some other way to retain the control data that you would suggest?
I would not recommend using the Session to save this kind of info.
Drawbacks:
Opening multiple forms not possible;
Values in dictionary are not typed.
Solutions:
Save it in the database already, having status incomplete (use SessionId for example for the retrieval);
Store the info in the ViewState (it travels with the page);
Use a class and store it in the Session.
I am using views concept in my asp.net form control.my first view consist of a form to capture user details.when user press continue it will move to the second view.
The problem is ,When user press the back button of the browser from the second view it doesn't move the the previous view instead move to the previous page in the browser history.
I wanted to move to the first view with the existing data in the form,when user press the back button of the browser.
You should perform a full page postback I guess, so that at client end your previous view will be saved in browser's history.
http://binaryjack.com/userControl.aspx
Each record is displayed using a user control. I have the delete button embedded in the user control.
Recreate Problem: click the first DELETE button, the last row gets deleted; after this I have to click the delete button (any of them) twice to make it work.
Is it bad practice to use a User Control (combined with a placeholder) to display a bunch of records? I query to get all records and then use a Foreach loop to populate each User Control and insert each UC into the placeholder.
Why does the Delete button not respond correctly?
Without seeing your code it is tough to say. However, it appears to be a refresh issue. If you hit delete then hit refresh, the record is gone. Check how you are refreshing the data and you'll find the issue.