C / C++ / MFC

dekta wrote:

BSTR Message;
char *buff = "This works fine" ;
Message = SysAllocStringByteLen (buff , lstrlen(buff));
return Message;

dekta wrote:

CHAR theChar;
CHAR* pChar = &theChar;
res = VarI1FromUI1( GETvst[10],pChar);
Message = SysAllocStringByteLen (pChar, lstrlen(pChar));
return Message;

extern "C"
{
	VARIANT WINAPI MyString(void)
	{
		
	
		unsigned char vst[21] = 
		{
			0x00, 0x17, 0xFF, 0x00, 0x17, 0xFF, 0x00, 0x17, 0xFF, 0x00,
			0x00, 0x17, 0xFF, 0x00, 0x17, 0xFF, 0x00, 0x17, 0xFF, 0x00,
			0x00 // null
		};

		OLECHAR olec[21];
	
		MultiByteToWideChar( CP_ACP, MB_PRECOMPOSED, (LPCSTR)&vst, 21, (LPWSTR) olec, 21);
		
		VARIANT vt;
		VariantInit( &vt );
		vt.vt = VT_BSTR;
		vt.bstrVal = SysAllocStringLen(olec, 21);
		return vt;
	}
}

Private Declare Function MyString Lib "DllString" () As Variant


Private Sub Form_Load()
  Dim n As Long
  Dim p
   
  p = MyString()
   
  For n = 1 To Len(p)
    Debug.Print Asc(Mid(p, n, 1))
  Next
  
End Sub

0
23
255
0
23
255
0
23
255
0
0
23
255
0
23
255
0
23
255
0
0

siaswar wrote:

I mean the better compiler,some compiler donot support some code's.

_asm<br />
{<br />
// Your assembly code goes here<br />
}

When a file is opened with the "a" or "a+" access type, all write 
operations occur at the end of the file. The file pointer can be 
repositioned using fseek or rewind but is always moved back to the end of 
the file before any write operation is carried out. Thus, existing data 
cannot be overwritten.

When the "r+", "w+", or "a+" access type is specified, both reading and 
writing are allowed (the file is said to be open for "update"). However,
 when you switch between reading and writing, there must be an intervening 
fflush, fsetpos, fseek, or rewind operation. The current position can be 
specified for the fsetpos or fseek operation, if desired.