FiveTech Software tech support forums

... are fields longer than 256 characters, the information in subsequent fields is returned truncated. Thinking that the reading that ADO performs is sequential and when it finds a field greater than 256, it begins reading the next field in the next bit of the file and for this reason it is truncated, ...

... I use tAds that I authored, which has the same logic as tDataBase. The best way I found to resolve these types of conflicts were: 1- For sequential numbers never to be chosen by the user. 2- Auto increment or any sequential number always after rLock() In practice I use a table of traffic ...

... calculate and put the number in the buffer, then save the full record, and unlock the file. 3). MY PREFERRED METHOD: Your goal is to have unique, sequential, numbers. I have a "counters" file. When I want to add a record, I open the file, get the proper value ( there are fields for each ...

... calculate and put the number in the buffer, then save the full record, and unlock the file. 3). MY PREFERRED METHOD: Your goal is to have unique, sequential, numbers. I have a "counters" file. When I want to add a record, I open the file, get the proper value ( there are fields for each ...

I think you could show us a step-by-step to develop with mod harbour. Nowadays, we have to search in forums and read a lot of topics, information that aren't sequential. It's hard to understand. Maybe a topic like Mr Rao did to FWHMYSQL.

... to remove it due to the countless problems both with tdatabase and with tdata. What countless problems? I have never had a single problem using a sequential primary key. Yes, I know you and nages gave me many examples last year but then on the net all this becomes very difficult. Why? I think ...

... disk" reveals that our testserver seems to be rather slow with disk read/write operations: Disk Random 16.0 Read 64.34 MB/s 6.7 Disk Sequential 64.0 Read 93.63 MB/s 6.4 Disk Sequential 64.0 Write 90.37 MB/s 6.4 Average Read Time with Sequential Writes 0.551 ms 7.9 Latency: 95th Percentile ...

... not understand why any government would care about the ID number ( used for linking a customer to other data ) assigned, and insisting they be in sequential number plus date time order. ( I'm not being argumentative. I just don't understand that point with customer ID numbers. ) 2). I do understand ...

... the ID on the new record data entry screen isn't always the ID in the record. Number 3 and 4 probably don't meet the regulations due to lack of sequential IDs in the physical order (not indexed) of the database. Also I believe you have to store the date and time in each record and these would ...

... are built differently than what you want. ID's are only assigned when a new record is saved. Thus, there are never any lost IDs and they are in sequential order in the file. For the sake of others reading this, Silvio's system gets the next ID from the database by adding 1 to the last used ID ...

... are built differently than what you want. ID's are only assigned when a new record is saved. Thus, there are never any lost IDs and they are in sequential order in the file. For the sake of others reading this, Silvio's system gets the next ID from the database by adding 1 to the last used ID ...

... an ID number for new record data entry screens because the record does not yet exist. When the new record is saved, it automatically gets a new sequential number. If the user cancels, then there are no orphan numbers unlike your current system. Please do not insist that Nages has succeeded in ...

... an ID number for new record data entry screens because the record does not yet exist. When the new record is saved, it automatically gets a new sequential number. If the user cancels, then there are no orphan numbers unlike your current system. The question is very simple. In Italy the invoices ...

... discussion on the forum of the customer number you answered that you don't use the code for the customer, instead I have to have it and it must be sequential because the law imposes on me the same way the progressive number of invoices. Let us admit that you use Tdata and your operator cancels ...

... + ;                "SELECT LAST_INSERT_ID()" )return oCn:aNext[ 1, 1, 1 ]  where the table `sequences` maintains sequential ids for different tables. This function also is network-safe (multi-user). This is a small example using this function to maintain `id` of ...