Entering Records at Top of Browse

[DORaymond]

I have an embedded browse on a simple form. The browse is sorted by a date field descending. Is it possible to have the new record pointer stay at the top of the browse instead of the bottom? In other words, if there is a long list of records in the browse, and the most recent record is at the top, is it possible to enter the next record literally at the top of the list rather than the normal action of the pointer dropping all the way to the bottom of the list?

Thanks,
Don

[Stan Mathews]

Re: Entering Records at Top of Browse

Don't think so. Records are always entered at the end of the table. Sorting the browse descending only presents the entered records for viewing.

[Ted Giles]

Re: Entering Records at Top of Browse

Don, I often have a form with both the current record, and where you can also enter a record, with the browse also shown.
Then whatever is clicked on the browse is displayed in the single record.
Selecting Enter New Record will save going to the end of a long browse chain. Just put it straight in.
You could possibly put a OnDblClick in the browse to fire a New Record process. On save, set index to recno or what ever, descending

[G Gabriel]

Re: Entering Records at Top of Browse

You could do this in a round about way:
1-Enter a record with a date far in the future and all other fields empty
2-Instead of just using a descending order for the date, use a filter with also a descending order for the date but with one of the other field that's is always filled as not blank. In this case that record will be filtered out and would not not show in the browse
3-On adding a new record: Change the filter to show all records with the date in a descending order, and instead of adding a new record, edit the record with the date far in the future as if it is the newly added record. Your script could change the date to whichever date you want
4-On saving the changes, add a new record with a date far in the future and change the filter to filter it out.

[Mike Wilson]

Re: Entering Records at Top of Browse

Have an xdialog box open at the top of the browse that simulates a browse row and enter the records into the dialog.

Gabe,
I can think of just about any way to get to a work around for stuff, but I don't hold a candle to your ingenuity! Love reading when you get creative!

[MoGrace]

Re: Entering Records at Top of Browse

Gabe's idea is interesting. But before I went to all that trouble, I would reconsider whether or not my layout could present the list in a more user friendly way if new records are to be added to the list with the full list in view too. An example would be a check register and a detail view of a check in the list. Sure, you could add a check to the end of the register, but presenting a different form for the individual check might be needed as well for editing or adding a check.

[G Gabriel]

Re: Entering Records at Top of Browse

I think somebody asked a similar question in the past and I posted an example with a different idea that I just remembered but it has been a very long time ago, so it might have been a different version of this. At any rate:
1-Leave your browse as is
2-Add yet a second browse on top of that one (overlap it) and make it invisible
3-Make the top browse only one row deep with no headings
4-When adding a new record, make the top browse visible. When saving, turn it invisible and resynch the form.

[G Gabriel]

Re: Entering Records at Top of Browse

Thanks Mike. Your candle burnt long before your legend ever did.

[DORaymond]

Re: Entering Records at Top of Browse

Thanks for the advice guys. I ended up doing it a different way. The descending sorted browse only has 5 fields and I put this browse on a form. I then placed 5 variables for these fields above the browse where the new "record" is entered. I then put together an append operation that adds the data when the save record button is pressed. Works well.

On Hold.jpg

[GGandhi]

Re: Entering Records at Top of Browse

I think your solution is probably the right thing to do.
I don't work with desktop. but in my opinion, the browse is for showing the data and forms are to enter the data as well as xdialogs.
it makes it cleaner and there have been lot of discussion about problems with browses when used to enter the data in this board.
look at many pos systems, that's how they do it.

[MoGrace]

Re: Entering Records at Top of Browse

You don't have to use variables, you can place actual fields from the browse on the form. Control new records with a button, then save the record and it will appear in the browse, with the pulled out fields on the active record.

[Nick Oldfield]

Re: Entering Records at Top of Browse

I think your solution is probably the right thing to do.
I don't work with desktop. but in my opinion, the browse is for showing the data and forms are to enter the data as well as xdialogs.
it makes it cleaner and there have been lot of discussion about problems with browses when used to enter the data in this board.
look at many pos systems, that's how they do it.

Yes, I NEVER EVER enter data in a browse. Always have a separate form (or xdialog) for entering the new data, then refresh the browse on exit from the form. (Almost) everyone on this forum recommends that approach.

[Keith Hubert]

Re: Entering Records at Top of Browse

Hi Don,

As Nick has suggested, I am in the same camp that recommends a separate form to enter data to a browse. Here is some very simple but powerful code which goes on a button to open the required form which automatically creates the child record.

'Get 'Value' property of 'Inv_no' in Form 'Invoice_new' .
DIM SHARED vc_inv_no AS n
vc_link_field = parentform:your_link_field .value
Dim linkdef as c
linkdef="your_link_field = "+s_quote(vc_link_field)
Dim P as p
p=form.ViewLinked("form_for_child_records",linkdef,"","","dialog_newrecord")

As the form is opened as dialog, the user cannot navigate away from it until completed. The developer sets all the criteria of which fields must be filled, etc.

ps. Change the variables and child form name to suit.