 |
CeRapiInit
..msdn Add comment W32 Constants Translate this page |
|
|
|
This function attempts to initialize the Windows CE remote application programming interface (RAPI). |
|
|
| Code examples: |
|
|
|
|
|
| Declaration: |
|
|
HRESULT CeRapiInit(void);
|
|
|
|
| FoxPro declaration: |
|
|
DECLARE INTEGER CeRapiInit IN rapi
|
|
|
|
| Parameters: |
|
| None. |
|
|
| Return value: |
|
| S_OK (0) indicates success. E_FAIL indicates failure. |
|
|
| My comment: |
|
The functions CeRapiInit or CeRapiInitEx must be called before any remote API calls can be performed. They initialize the underlying communications layers between the desktop computer and the target device.
A call to CeRapiInit does not return until the connection is made, an error occurs, or another thread calls CeRapiUninit.
I see no reason of using the CeRapiInit in FoxPro code because of its blocking nature. Once you call this function with no mobile device connected -- your application is frozen forever. The non-blocking CeRapiInitEx followed by the WaitForSingleObject call works very good.
Call CeRapiUninit even if the connection failed. |
|
|
| Word Index links for the CeRapiInit : |
|
|
|
|
|
| Translate this page: |
|
|
|
|
| • |
|
| Created: | 2004-06-20 13:20:56 | | Modified: | 2004-06-30 11:20:17 |
Visited in last 7 days: 15 |
