FiveTech Software tech support forums

... of the Edit_Comuni() function. When you set a keyboard shortcut using SetKey(), Harbour will wait for the user to release all keys and then execute the code block associated with that shortcut. In this case, "KL" is an arbitrary shortcut that is not likely to be pressed by the ...

... of the Edit_Comuni() function. When you set a keyboard shortcut using SetKey(), Harbour will wait for the user to release all keys and then execute the code block associated with that shortcut. In this case, "KL" is an arbitrary shortcut that is not likely to be pressed by the ...

... the buttonbar based on the overall selection state of the xbrowse. As for the double-click issue, it's because the `:bLDClickData` block is being executed immediately after the selection is toggled. To fix this, you can add a small delay before executing the `Edit_Comuni` function. Here's an example: ...

... I only use version 10 of the client regardless of server version ( >=10 ). All improvements since version 10 are on the server side and you can execute all of them from any client user the corresponding stored procedure "sp..." function. Reinaldo.

... Your example is longer but the same as my original sample as far as vertical oriented text is concerned, You are missing the real point. If you execute the program on a computer where MSWord is installed, you can not see the vertical text in the PDF. You see the vertical text in PDF if (1) MS ...

... Your example is longer but the same as my original sample as far as vertical oriented text is concerned, You are missing the real point. If you execute the program on a computer where MSWord is installed, you can not see the vertical text in the PDF. You see the vertical text in PDF if (1) MS ...

When you face such problems, I suggest you compare the
oCn:InsertSQL( ... )
with
oCn:CreateTableSQL( <table> )

or
Please create a small sample that we can execute at our end on the above cloud server.

Lastly, If we do not like to use FWH's error handling and like to have our own error handler Then at the beginning of the application, execute ErrorBlock( { |e| MyErrorHandler( e ) } ) and have our own error handling module like "errsysmy.prg" with this ...

... a RowSet is opened for ReadOnly, again the initial reading is faster. oRs := oCn:RowSet( cSql, [aParams], [lReadOnly] ) Execute aData := oCn:Execute( cSql, [aParams] ) We get the data in a multi-dimensional array. In case we need the structure, call this ...

... a RowSet is opened for ReadOnly, again the initial reading is faster. oRs := oCn:RowSet( cSql, [aParams], [lReadOnly] ) Execute aData := oCn:Execute( cSql, [aParams] ) We get the data in a multi-dimensional array. In case we need the structure, call this ...

... Here I use a Xeon CPU (iMac) and nvidia GPU (RTX 3060, eGPU). If I build it locally it will not be able to properly execute on a lower CPU/GPU. Thats why you have to build it yourself on your own CPU and GPU. AI gets it best speed using nvidia GPU. Also enough RAM ...

... libres y despues de leer sus registros encryptar nuevamente?, .Adt´s. Pues me lanza un error cuando lo hago de la siguiente manera : getConexion.Execute("EXECUTE PROCEDURE sp_DecryptTable('Tabla.Adt','12345678');", out iFilasAfectadas, -1); getConexion.Execute("EXECUTE PROCEDURE ...

... Error: LOCAL declaration follows executable statement operation: line:593 called from: HB_COMPILEFROMBUF, line: 0 called from: ..\source\exec.prg, EXECUTE, line: 68 Source: 0066: cPRGPATH := hb_GetEnv( "PRGPATH" ) 0067: cPRGPATH := STRTRAN( cPRGPATH , "/", "\" ) 0068 ...

... Error: LOCAL declaration follows executable statement operation: line:593 called from: HB_COMPILEFROMBUF, line: 0 called from: ..\source\exec.prg, EXECUTE, line: 68 Source: 0066: cPRGPATH := hb_GetEnv( "PRGPATH" ) 0067: cPRGPATH := STRTRAN( cPRGPATH , "/", "\" ) 0068 ...

... ID for a file. Here's a simple example of how you might retrieve a file's ID using the fsutil command: 1. Open Command Prompt as Administrator. 2. Execute the command: ```cmd fsutil file queryfileid C:\path\to\your\file.txt ``` Replace `C:\path\to\your\file.txt` with the actual path to your file. ...