FiveTech Software tech support forums

Question : what is 8th Element of ROW from ::aStructPG for :?: In cases of SQL like this SELECT first AS firstname, ... Column 1 shows "firstname" and column 8 shows the actual name of the field, i.e., "first" So, we need to use column 8 only for building ...

... they are in the initial cdx, they will be active all the time. Is it adviced that we only make a index for the CDX for main Tags like, code, name, firstname and for all others make a temp index (even with the tmp clause) that i discovered. they will be active all the time. Whether you use a filter ...

... they are in the initial cdx, they will be active all the time. Is it adviced that we only make a index for the CDX for main Tags like, code, name, firstname and for all others make a temp index (even with the tmp clause) that i discovered. Except that there is one 1 call when we open the cdx over ...

... for that customer and the CUSTNO gets added automatically to the reservation database. CUSTOMERS.DBF FIELDS: CUSTNO (primary key, unique) FIRSTNAME LASTNAME RESERVS.DBF FIELDS: (You could have multiple reservations for the same CUSTNO) RESERVNO (primary key, unique) CUSTNO RESERVITEMS.DBF ...

... that there was a positive result found. {"status":200,"data":[{"customerId":1,"gender":"","firstName":"Marc","lastName":"Venken","dob":"0000-00-00","emailAddress":"marc@maveco.be","addressBookIds":"2","defaultBillingAddressId":2,"defaultDeliveryAddressId":2,"phoneNumber":"89853445","faxNumber":"","bankAccountNumber":"","subscribedToNewsletter":"0","guestAccount":1,"approved":1,"discountGroupId":0,"discountGroupName":"","groupDiscount":"0.00","numberOfLogins":1,"lastLoginDate":"2014-09-11 ...

... "token: c5ce13c97e79b8d54ca40e75ea43c41282cb25e469c4babb8ad4400850a54624" -H "Content-Type: application/json" -d "{\"firstName\":\"Marco\"}" and Request Url : http://swagger.shoptrader.com/api/v2/customers/1?token=c5ce13c97e79b8d54ca40e75ea43c41282cb25e469c4babb8ad4400850a54624 ...

... ejemplo Gracias nuevamente. USE CUSTOMER XBROWSER "CUSTOMER" COLUMNS "FIRST","LAST" SETUP oBrw:cHeaders := { "FirstName", "LastName" }

... the list in that order and I start typing in the info. Thus, to do a search I popup the browse, click on the company field ( remember, last name + firstname or the actual name of a company ), and start typing the first few letters. The browse moves to that position instantly. For efficiency, if ...

oCn:RenameColumn( cTable, cOldName, cNewName )
oCn:AddColumn( cTable, aColSpec )
oCn:AlterColumn( cTable, aColSpec )

aColSpec ( dbf column spec )
Eg:
{ "firstname", "C", 30, 0 }

{ "salary", "N", 10, 2 }

etc

... we can omit them. Example: if the Header is "First Name", following are valid: oBrw:oCol( "FIRST name" ) oBrw:oCol( "firstname" ) oBrw:oCol:firstname. When there are duplicate names, it is safer to refer them with nCreationOrder. There can be same header name ...

... This never fails. If the browse is something like: @ r,c XBROWSE ..... COLUMNS "FIRST", "LAST", ......... HEADERS "FirstName", "LastName", ....... Then condition like oBrw:FirstName:Value = <something> is better than oRs:First value or oRs:Fields( ...

... Death Indicator The make up of the patient name is in XPN format as follows: SEQ LENGTH DT OPT TBL # NAME XPN.1 194 FN O Family Name XPN.2 30 ST O FirstName Given Name XPN.3 30 ST O Second And Further Given Names Or Initials Thereof XPN.4 20 ST O Suffix (e.g., Jr Or Iii) XPN.5 20 ST O Prefix (e.g., ...

... "2014-12-16T10:58:52.293529Z", "UserDetails": { "ContactID": 674, "AgentID": 184145, "FirstName": "UAT", "LastName": "APIUser", "Email": "UAT.apiuser@company.com", "JobTitle": ...

... This might sound odd but the real purpose is this. The sql statement creating the rowset could have used alias names for the fields, eg: FIRST AS FIRSTNAME, LAST AS LASTNAME, HIREDATE AS JGDATE, etc. The rowset displays the alias names only eg. FirstName, LastName, JgDate, etc but not the original ...

... that single tables can be edited/modified easily. In addition even the following types of queries are editable. SELECT id AS CustID, first AS FirstName, last AS SurName from customer. Though the field names used in the rowset are CustID, FirstName, SurName any modificatiosn to these fields ...