FiveTech Software tech support forums

... If you omitted this xbrowse would display the default alias. If this is a bug, has it been corrected? If it is not a bug, then how can I get the CUSTNO of the currently selected record? There is no bug at all either in xbrowse or tdatabase. Hence, no need for correction. Please re-check your ...

Try with

Code: Select all  Expand view

oBrwCust:custno:Value
 

(adapt custno to the name of the desired column)

... in the indexed database, NOT the currently highlighted record in the xbrowseoBrwCust:bLDblClick:= {| oCustomers | msgInfo(oCustomers:custno), msgInfo(oCustomers:last) } I would assume that when you left-double-click on a record in an xBrowse it would become the "current" ...

... If it is not, then that is why the search is failing. Also, why do you even need to find if a customer's name already exists? If you use a CUSTNO then this doesn't matter--you can have ten customers with the same first and last names--they will each have a different CUSTNO. You just link ...

... RETURN NIL ENDIF oCustomer:Load() cTitle := "Modify Customer" ENDIF define dialog ... REDEFINE GET oGet[1] VAR oCustomer:custNo ID 101 OF oDlg UPDATE WHEN .F. sample FUNCTION CreateCode( cDoc )   LOCAL oControl   LOCAL cDoc oControl := ...

... there is an error because I use an old release of customer not have the field ID but it make the same the index Index on "id" tag "custno" to customer as you can see on this picture https://i.postimg.cc/Y0Rhy96S/hhhh.jpg How it can happen ? Dear Enrico ( Emg) ...

... Change for example "CUSTOMER" to "XXXXXXXX" (any text) as well as the names of the fields, for example "CUSTNO" by "Customer Number". I have ruled out the use of lib compatibility mode. of Sergey since I have seen that the SetWorkArea method ...

... data (and saves it too) in the customer table. No PUBLICS or PRIVATES are used. To instanitate this object all you need one line of code and the CustNo. oCustomer:= TCustomer():New(cCustNo) That's it! Now you can query the object for any info it contains (which can include complex calculations ...

... name fields which can create all kinds of problems. These are all very good reasons for always using ID numbers for primary keys. I would have a CUSTNO (or similar) in both files. And not allow users to change them. I am planning to do some speed tests with a DBSetRelation() & setScope() ...

... a customer has 7 phones then you have to restructure the customer file. If you use a one-to-many relationship, you create a file with two fields, custno, and phone. You can have an unlimited number of phones for each customer. CUSTNO, PHONE 01111, 124-9999 01111, 124-9995 01112, 678-0000 In this ...

Richard, Hmm. I have questions. Are there two fields named CUSTNO and NO in both the cust and bill file? If so, is the CUSTNO relevant in some way, or do you just want to delete all the data in the NO field from Cust file for any NO data that exists in ...

Richard, Hmm. I have questions. Are there two fields named CUSTNO and NO in both the cust and bill file? If so, is the CUSTNO relevant in some way, or do you just want to delete all the data in the NO field from Cust file for any NO data that exists in ...

... local oDlg local oLbx DEFINE DIALOG oDlg FROM 0, 0 TO 26, 79 ; TITLE "Print" @ 0.2, 21 LISTBOX oLbx FIELDS &FIL->custno,; &FIL->name, &FIL->area,; &FIL->agent; HEADERS "Account No", "Name", "Area", "Agent" ...

Here's a template example of possible usage: ------------------ ... ... REDEFINE GET oMYGet1 VAR CustNo ID 101 OF oDlg UPDATE VALID {|oGet|GENERALUDF(oGet)} REDEFINE GET oMyGet2 VAR PostCode ID 102 OF oDlg UPDATE VALID {|oGet|GENERALUDF(oGet)} REDEFINE GET oMyGet3 VAR ProductNo ...

I have created the following stored procedure which works but is just as slow as 32 seeks Any ideas Use iwscompa go IF OBJECT_ID ('usp_find_price') IS NOT NULL DROP PROCEDURE usp_find_price go CREATE PROCEDURE usp_find_price @mSite numeric(2), @mCustType varchar(10), @mCustNbr varchar(10), @mUniqNbr...