Silvio, >how can i do this check and see that the name entered is already in the archive? This is a classic problem when you are not using unique primary-keys. Primary-keys are one of the basic principles of relational-database programming. Another principle is to store each piece of data, ...
... ) // where fieldname is an actual fieldname. Does that work? Also try: MsgInfo(oDBF:nArea) Note that TDatabase creates it's own unique workareas which is not going to be 9 in this case. With database objects you never deal with workareas. Your error message: Error description: ...
... reloading or may need to synchronize modifications, f.e. unlock. You can simulate it in many different ways, f.e. by skip(0). The 2-nd action is unique to dbcommit and it's not necessary for any synchronizations in simultaneous/concurrent/network access. The whole job here is sending information ...
... oCustomer object (single customer not a table) as a variable of the invoice class. Note also that the database objects handle finding and using a unique workarea so you never have to deal with workareas again. oInvoice:= TInvoice():new(cInvoice:ID) MsgInfo( oInvoice:oCustomer:name ) To do this ...
... an error (in my case, because the code already exists). In this case, the values of the oRs variable are lost. The code field has created a unique index on the server. I could carry out this check, but I prefer to control it more securely at the database level, because the application can ...
... A priori, y si no da ningún error el servidor, funciona perfectamente. El problema está en que la tabla que estoy manipulando, tiene un indice UNIQUE en el campo Codigo, con lo cual si intento crear un registro con un código existente, me da error, pero el problema está en que es como si el ...
... the record. oRs:Save() If the server does not give any errors, it works perfectly. The problem is that the table I am manipulating has a UNIQUE index in the "Codigo" field, so if I try to create a record with an existing code, it gives me an error, but the problem is that it ...
... allows you to decide which form(s) to print The data for that specific job is then applied to each form and it outputs them. Each form can have a unique design based on the needs and requirements of the client, or even the government. Tim Tim, or example, on any workorder, there are 3 options: ...
... allows you to decide which form(s) to print The data for that specific job is then applied to each form and it outputs them. Each form can have a unique design based on the needs and requirements of the client, or even the government. Tim
You can also avoid these kinds of problems by using database objects. Every database object creates its own unique workarea and handles it internally. Thus you never have to deal with workareas.
Thanks Mr. Rao Two questions 1.- oRs:ID return 'the object not exist' oRs:Fields( 'ID' ):Value is unique form? 2.- If I need Find/Seek; what can I do the seek? Or tell me where read
... there is no way to retrieve the used function from the codeBlock. Anyhow, you can use the function __vmItemId( codeBlock ) to check the codeblock unique ID: function Main() local bErrorBlock := { || nil } ? __vmItemId( bErrorBlock ) ? __vmItemId( ErrorBlock() ...
Do you mean we don't need index other than a primary key? a) We need to create unique indexes for enforcing unique constraint for a column or set of columns. If we want to create unique constraint to a single column, we can either create while creating the table ...