Hello Robert -

I'm sorry to see that you have not had a response to this. But I understand why .. I had to read your message more than once and I'm still not sure I understand the question.

If I understand it correctly ..
On a form you can bind several LE's to the same field. Same data. When one changes the others change. But that's not what you want. You want to capture the current data and show it in alternative fields. So there's a "Current name" field and a Current Name LE, then a "Original Name" LE. You want to click on a button and 'capture' the Current Name and show it in the "Original Name" LE. If someone subsequently changes the Current Name you want the new name to show in the Current Name LE but the Original Name LE to remain unchanged. To do this there is no alternative to having fields for both - Just as you would have done in Q&A. Have your command button copy the contents of CURRENT FIELD into ORIGINAL FIELD when you want. You don't need XLookup, just something like..

cmdCaptureName - On Element Entry:

Original Field = Current Field
ReadOnly(cmdCaptureName, 1)

Sorry about the confusing explanation.

Alec you have the concept of what I want to do. My original thought for a solution was exactly what you explained but at least for me (I might be doing something wrong) It will not work as you described using Alternate form.


When working in Sdesigner  on the alternate form in the same database you can not use

Original Field = Current Field

Original field (the field or element from the other form in the same database) is not valid in the alternate form (I had thought it would have been) So I am forced to do a lookup of some sort.

I would love for someone to tell me I am wrong about this and tell me what I am doing incorrectly, because it would be ideal if as I had hoped the elements or fields were interchangeable on all forms in the same database.

As stated in the previous post you can bind a new element to a field in the same database, but this would mean I would need 2 elements for every field I want on my alternate form. In your example Alec I would first need to make a new element on my alternate form bound to original field and then another element on my alternate form called current field then I could use Original Field = Current Field. Then I end up with 3 fields in the same database to achieve my goal.

Hello Robert,

A Form or Report can only see those elements which are physically on it, so Original Field = Current Field  will not work if one of those elements does not exist on the form where the programming exists.

If you do not want to have other Layout elements bound to the underlying field then, Yes you will need to use a X command and probably either @XResultSetSearch() or @XLookupSourceList()

-Ray

Hello Robert,

If you are worried about Application size then go with an X command. As for speed, I can not say which one would be faster, as I am not sure.

btw I figured out a neat little way to get field values from the underlying database. It can be seen below. Since the XResultSet commands work on the Database themselves and not on the form, they are more powerful than the normal X commands.

The code below is for a second form in the Customers database in the samples Customers.db file. It has an unbound element named company on it, but it grabs the value from the database field company and fills in the element.

Var vRS as Int
Var vCurPos as Int

vRS = @XResultSetForm("")
Company = @XResultSetValue(vRS, "Company")
XResultSetClose(vRS) 

-Ray

BOBSCOTT wrote on Jul 17^th, 2007 at 9:20pm:


Thank you.

Quote:


No problem.

vRS = @XResultSetForm("") 

This gets the ResultSet from the current form. So if you have retrieved 10 records in Search/Update, your XResultSet will have the same 10 records. If you are on the 5th record in Search/Update, you will be on the 5th record in the XResultSet. Since the XResultSet commands act on the database they have access to every field in the database for any particular record.

LDF_1a = @XResultSetValue(vRS, "propertylast") 

This gets the value from the propertylast FIELD for the current record and places it in LDF_1a ELEMENT on the current form.

XResultSetClose(vRS) 

This closes the XResultSet which is a necessary step when working with XResultSets.

Anything I need to clarify more?

-Ray