FiveTech Software tech support forums

... table with its alias "H". I think it is something related to XBROWSE. Perhaps the master Rao can shed more light on this. H and S are aliases to indentify LEFT and RIGHT tables (hdrvda and sucursales in your example). Each field in table hdrva will be invoked with prefix "H.": ...

Jose, I'm still not sure what you try to do If you use aliases, maybe it is better ? I don't think that you wanne go into database object. Here a code that look like yours. Please feel free to post if I understood you wrong.          netopen("artikel","artcode","arttemp")  ...

Temporary indexes do not affect the main cdx file. They are available for use in the work area (alias) where created and not available for other aliases of the same dbf. They are created as temporary files and deleted when the alias is closed. They are also called memory indexes. In the command, ...

Temporary indexes do not affect the main cdx file. They are available for use in the work area (alias) where created and not available for other aliases of the same dbf. They are created as temporary files and deleted when the alias is closed. They are also called memory indexes. In the command, ...

... like below. I substituted oLineItem for cAlias) and oPart for the "nofoto" alias. Note that with objects you don't ever need to use aliases. And it is much easier to understand when you use real world terms.            oLineItem:bedrag  := oPart:bruto           oLineItem:aankoop ...

... if the alias "CONSORC" is not already in use. If that alias is already in use, it returns "CONSORC001" If both the aliases "CONSORC" and "CONSORC001" are already in use, it returns "CONSORC002". This function always returns an alias ...

There is no need for using Aliases in ADO.
We can open any number of recordsets for the same table at the same time and each recordset acts like different alias for dbf.

... dbClosearea() )ListO->( dbClosearea() )     Regards. Jose. Are you sure you are not closing the aliases inside oRepAa:bEnd also?

... to create a new method OrdSetFocus() that works like you want but using OrdScope() to accomplish this. Note that you don't need to use any aliases or workareas with database objects. That is all handled automatically by the object.

Hello everyone I would ask for further clarification on these aspects: 1) Is it possible to open multiple cursors (aliases) for the same table?     E.g. (x)Harbour LOCAL cALIAS1 := cGetNewAlias("CUSTOMERS")            ...

* New: function FW_DBFLOOKUP( uVal, [cOrder], bcRetExprn ) --> uResult uVal : Value / Expression to be lookedup ( seek or locate ) cOrder : OrderName for seek. Or field name for locate. Omit if uVal is an expression bcRetExpr: codeblock/string: Expression to evaluate Examples: CUSTOMER->( FW_...

This is easy

2. I can open de database in more aliases and use different browses and lookups with these aliases ?? Can I get issues with the CDX file ?

No problems.

Marc, You gave me a laugh when I saw your message directed at me-you knew I would say OOP. Good, at least you remember. Note that back in Clipper era with 16bit computers without much memory we were limited as to how many files we could have open at one time. This rarely an issue now. so you can ope...

But just out of interest... witch is used more often here ( 1 or 2) ? Personally, I'm using both, depending on the specific situation. In 1 : The first time, sometimes is with a relation set to ... , and when the database order is changed, the relation is broken. (I believe this is standard in FW) ...

... can change the index order, but than I also have to keep track of resetting it back and at the correct position 2. I can open de database in more aliases and use different browses and lookups with these aliases ?? Can I get issues with the CDX file ? And we can use Oop (James), smaller parts are ...