FiveTech Software tech support forums

... network compatible. Open a file object with one line of code. Databases are open in shared mode, buffered, optimistic locking, no dealing with aliases workareas, etc. Use this with the customer.dbf file you recently sent me and/or change it slightly to work with any database. /*Purpose  : Showing ...

... some timeoCustomer:save()  You build in a check in the save() method to prevent creating a duplicate record. Note that aliases and record locking are built-in, so you don't ever have to deal with them. However, your example is not a good one. You should never use something ...

... ALIAS 'STK_MOVSTK'RETURN Self....  Toda entrada o salida de stock va por este servicio, que tiene abiertas las tablas que usa en sus propios aliases, y sus métodos no alteran ninguna workarea que no sea las propias, con lo que no me afecta el resto del programa. Lo mismo se podría hacer para ...

... // pass a payment objectoCustomer:End() Note that you can pass objects to functions or other objects without dealing with any workareas or aliases. Very useful. Regards, James

... One of the advantages of database objects is that you don't have to deal with workspaces and aliases. These are handled automatically. Also you don't need scatter/gather routines--again handled automatically. And code is much easer to read since ...

... have to open either the customer database or the dial database. Nor do you have to remember which indexes to set. And there are no work areas or aliases to worry about. Finally, you don't have to remember to save the phone numbers to a different database. All you have to do is: oKlants := TKlants():New() ...

... any info it contains (which can include complex calculations and reports). Everything is encapsulated so you don't have to worry about workareas, aliases, or variable name conflicts. You can also do a series of field updates with one call: oCustomer:applyPayment( nAmount, date() ) This updates ...

I also like to use server aliases to avoid all those long path names. On adsserver.ini have this line: [ServerAliases] Mp10=/long path name Now change your long path name to Mp10. That's all. BTW, you don't need to share the directory. ...

... that allows a dicotomic search of symbols. This subsystem is responsible for quick access to symbols (functions, variables, fields and workareas aliases). e.. The static and public variables: Responsible for storing public and static variables. The CVM uses two different Clipper arrays for this ...

... the DSN Driver: The name of the MariaDB ODBC Driver. Must be always {MariaDB ODBC 1.0 Driver} Server: name or IP of the MariaDB database server. Aliases: Servername User: user name for database authentication. Aliases: UID, Password: password for database authentication. Aliases: PWD Database: ...

... be present the min 4 first letters in ADO SET TEMPORARY NAMES... otherwise will never be opened. You can use this to check the status of tables,aliases, locks, relations and indexes per area. FUNCTION expalias()LOCAL cerrorlog := "",n,j,ntarget,x   for n = 1 to 255  ...

... the 1st index in the SET INDEX TO. Is it not working like that? Can you post an example? 2.) Opening the same DBF with 2 or more USE and different aliases is in other RDD possible. In ADORDD? It works like any other rdd you everything continues the same. My apps work just like that and its 100% ok.

... with SET INDEX TO .... In some cases this is required if i will not change the code. 2.) Opening the same DBF with 2 or more USE and different aliases is in other RDD possible. In ADORDD?

... it is not much of an issue because you are using oCust:id, oPart:id, and oInvoice:id, so the code is very clear and you don't have to worry about aliases. You also are going to need the "standard" HBRECNO auto-increment field so the tables work with ADORDD. Maybe you can specify a different ...

... can globally set them to open automatically whenever you open the DBF. Better yet, you should consider moving to database objects--no more using aliases or work areas. You can eliminate lots of code this way. This provides easier to read code with less bugs, and it is easier to maintain. oCustomer:= ...