FiveTech Software tech support forums

... that were loaded during the initialization process using WSAStartup(). These DLLs provide support for specific network protocols like TCP/IP. Cancels Pending Calls (with caution): It's important to note that WSACleanup() cancels any pending blocking or asynchronous Winsock calls issued by ...

... something similar to this? Best regards, Otto http://www.dbase.com/help/Xbase/IDH_XBASE_ROLLBACK__.htm Show ROLLBACK( ) Topic group Related topics Cancels the transaction by undoing all logged changes. Syntax ROLLBACK([<database name expC>]) <database name expC> The name of the database ...

... the ID displayed on a new record input screen. This is technically not possible, because you will end up with a blank record every time a user cancels a new record entry. Is that the issue you are referring to? And by the way, how are they going to respond to not even having a reservation number ...

... the user is left waiting Without knowing what to do. When that happens, and don't keep waiting, I have given the F12 key a bat 'cancel.bat', which cancels the 'FE.EXE' program with TASKKILL. The big question is: Is there a way to use a TIMER or something else to be able to control the response ...

... No changes are written to the server. These changes are also not visible to the other users on the network. Calling the method CancelBatch () cancels all changes and restores the data in the client's memory to the original state. Calling the method UpdateBatch () flushes all changes to the ...

... the system file nID: = oSys: id + 1 // increment the key field value by 1 if the saving is canceled by the user there must be another method which cancels the counter, ie it opens the sysfile file and saves nId: = oSys: = id-1// decrement the key field value by 1 when a user add a new customer ...

... that I will be able to see the last number, that is, only after the rescue, I agree very much but the question comes spontaneously if the operator cancels the entry and the Id on sysfile.dbf increases by +1 I will then have an illegal list of invoices with non-progressive numbers is this normal? ...

... the system file nID: = oSys: id + 1 // increment the key field value by 1 if the saving is canceled by the user there must be another method which cancels the counter, ie it opens the sysfile file and saves nId: = oSys: = id-1// decrement the key field value by 1 when a user add a new customer ...

... an alternate. My system keeps track of IDs in a separate file. I told him we could get the next ID and display it on the screen, then if the user cancels it, the ID is abandoned because it is never saved. These are the missing ID's Silvio mentions. This is the only solution I could come up with ...

... an alternate. My system keeps track of IDs in a separate file. I told him we could get the next ID and display it on the screen, then if the user cancels it, the ID is abandoned because it is never saved. These are the missing ID's Silvio mentions. This is the only solution I could come up with ...

... 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 this as well, if the user does ...

... did not write TData to do it. This is why your conversion is taking way longer than I expected. Let us admit that you use Tdata and your operator cancels the insertion of an invoice, losing the invoice number because in fact, according to James's scheme, if you do not save the invoice, later you ...

... 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 the insertion of an invoice, losing the invoice number because in fact, according to James's scheme, if you do not save the invoice, later you ...

... exist. It only exists AFTER the user saves it. If you assign ID's before the record exists, then you have to delete the blank record when the user Cancels instead of Saves. When you were writing code for only a single user this was not an issue, but with multiusers you cannot then open the file ...

... [nRecNo] ) nRecNo defaults to current record. Unlocks specified record only 76. ReIndex() ReIndexes the database. FWH 17.08 77. RollBack() Cancels any changes made to current record of DBF, pending commit to disk. See also ::Updated() 78. RowGet( cFieldList, lBlank ) Internal Used internally ...