FiveTech Software tech support forums

... next record: INSERT INTO mytable ID,..... VALUES ( 101, .... ) New record will be inserted with value of 101 for ID and subsequent inserts will be incremented from 101 onwards. Hope I am clear.

... ) ) --> nAge of ID 108 CUSTOMER->( FW_DBFLOOKUP( 99, "ID", "FIELD->SALARY += 100" ) ) --> Salary field is incremented and written to table and returns the value ITEMS->( FW_DBLOOKUP( 101, "ITEMCODE", { || FIELD->QTY -= nOldQty } ) ITEMS->( ...

... sequence numbers. All this logic is no more required if we use AutoIncrement fields. Here is the important difference: You are fetching the incremented value at the time of appending the record. Here we are required to fetch the incremented value in advance and display it in the Append Dialog ...

Hi Mr. Rao,

Everytime press + and cancel button id is incremented by 1. Is there any solution to increment when press cancel button?

Thanks.

... me ) decided to use a PK that was an auto Increment .. all the attacker needed to do is add records to tables ( inject ) and since the PK was auto incremented, there was nothing to stop the creation of new rows. If the PK were code driven .. meaning the PK was created by the developers code .. ...

... me ) decided to use a PK that was an auto Increment .. all the attacker needed to do is add records to tables ( inject ) and since the PK was auto incremented, there was nothing to stop the creation of new rows. If the PK were code driven .. meaning the PK was created by the developers code .. ...

... ) ) --> nAge of ID 108 CUSTOMER->( FW_DBFLOOKUP( 99, "ID", "FIELD->SALARY += 100" ) ) --> Salary field is incremented and written to table and returns the value ITEMS->( FW_DBLOOKUP( 101, "ITEMCODE", { || FIELD->QTY -= nOldQty } ) ITEMS->( ...

...   oFont:End()   Enddo  Mr Cristobal This is not a case of under release of fonts. This is a case where a font is released more than it is incremented.

... Notice placement is a calculation of the printer nHorzRez() and nVertRez() ( which it appears you are doing ) .. also Line spacing is incremented or de-incremented by the font:nHeight .. not very pretty, but it works with just about any printer and places your text and pictures in ...

... being renumbered)?   No, it is totally different than an auto-increment field. Yes, every time you update the record the rowversion field is auto-incremented. Let's say you have a sequences table (as you do) where you store sequences for each field of each table that is to be sequentially incremented. ...

... guarantee no one else has changed the field on a race condition. Just like auto-inc fields rowversion fields are maintained by the SQL engine and incremented anytime a record is updated. Here is the code which explains itself a lot better than words: //-------------------------------------------------//DECLARE ...

... all the fieldnames just so I could use Hungarian notation. I would change any that were necessary to avoid reserved word issues. As far as auto-incremented primary-key fields go--they worry me. Since as Reinaldo pointed out, they can get renumbered under several situations which could make your ...

... do not make good invoice numbers. If you ever merge data, replicate, res-structure, move records, you will not have any control over these auto-incremented values and they may reset creating havoc with child-relationships. If you still prefer to use auto-increment field as invoice numbers here ...

... care of releasing this font and there should be no problem. When we assign a font to header or footer or data, the font object's counter is not incremented. So xbrowse does not need to destroy the font.

... we are not creating a totally new object with totally new :hFont. This function actually returns the same object with its internal counter :nCount incremented. Actually, the internal method :Modify() achieves the same effect. oClone := Clone_Font( oArial ) // your method is exactly same as oClone ...