If all of these applications are identical, you may be better served using one application and placing a "client" element on the form, and using a query to work on each client in turn.

If all of these applications are identical you can use the "Export All to Text File" and the "Import from Text File" options in the File pulldown menu in the programming editor to export your programming from the master application and import it into each of the copy applications. In any case, do not use MSWord, it is not an ASCII text editor and may be munging your code. It is not made for *any* kind of programming and should not be used for ASCII data. Use a text editor instead of a word processor.

If all of these applications are identical in design, but different in data, you can simply reconcile to the others from the master DSR file, without having to cut and paste any code at all.

Do your XLookups have the filename of the application in them? If so, replace these with @Fn so they will work in any application even if it has a different name.

If you use @XLookup instead of using XLookup, you can return the value to a variable and check its value (and the value of @Error) before you assign the value to an element and overwrite the existing value. If the there is a choice between using a function and a subroutine, that are otherwise identical, always use the function and return the value to a variable.

Thank you both for your quick responce and ideas.  Although I can not reconcile some of the data straight to another database for a few changed cannot be unchanged, but the programming should be the same.  I backed up all my files, exported all programming data to text file.  I opended another database in Designer and deleted all programming.  Saved, and the imported programming from text file.  Saved, and reconciled with the .db file.  When I opened it to try it, I was still getting the same results.

I don't think that @FN applies to my @XLookup s.  I am having something looked up from outside of this application.  That way one application holds the same data for dozens of applications to access.  For Example:

vlook = @XlookupSourceList("data\worksheet.db",ThisElement, "worksht!work sheet", "DESC1;DESC2;DESC3;DESC4;DESC5;DESC6;DESC7;DESC8;DESC9;DESC10;DESC11;DESC12;DESC13;F0038;F0043;F0048;Procedure")
 

And

vemp = @XLookup("data\empno.db", ThisElement, "empno!Employee No.", "Employee Name")
 

That is odd.  The one looking up the worksht database says NO.
The one looking up EmpNo, shows nothing at all. and gets removed on the save.

var vemp as string

vemp = @XLookup("data\empno.db", ThisElement, "empno!Employee No.", "Employee Name")
writeLn(@Error)
Calibrated by Technician0 = vemp
 

This is the complete code that is in EmpNo Element Programming on Element Change.  I enter in a number for example "53" and it should put "James Jones" in Calibrated by Technician0 textbox.  Nothing happens to Calibrated by Technician0 and when i save record, EmpNo textbox that had "53" in it disappears.

Well that was exactly it.  Now that gives me one more thing to check first.  Thank You.

Calibrate1 wrote on Sep 28^th, 2006 at 5:46pm:



Elements aren't bound to elements. They are bound to a field in the underlying database. The element and the field may have the same name, but they are not the same thing.

In Designer, click the EmpNo element to select it.
On the Property Editor, go to the Other Tab.
From the Bound To dropdown, choose the field name whose data you want to see in the EmpNo element.
Click the Set button next to Bound To.
Check the Other Tab in the Property Viewer to make sure EmpNo is Bound To the correct field.
Save the Layout.
Reconcile to the correct db.