Prev: error code COOD1199
Next: LinQ. update column with auto generated value
From: Adrian Chen on 22 Jul 2008 09:34
I'am a beginner in ASP.NET, now I have a simple problem, I suppose, for you
but difficult for me.

I have a device connected with a client machine through COM1, now the client
gets binary from it, then how can I transfer them to the server machine
where the data will be stored in Microsoft SQL Server?

I use MSComm control to help me get the data. The point is the data that
serial-port device returns is 256 bytes long and is stored in byte array.The
type of data's corresponding field in database is binary.What would I be
careful of in order not to destroy the structure or content or format of the
data? I am worried that the .net will treat it as the unicode string or
something else and then will change something of the data.



From: Jim Rand on 22 Jul 2008 13:37
You might look at base 64 encoding.

"Adrian Chen" <aoopopopo(a)126.com> wrote in message
news:uFdIr%23$6IHA.4652(a)TK2MSFTNGP05.phx.gbl...
> I'am a beginner in ASP.NET, now I have a simple problem, I suppose, for
> you
> but difficult for me.
>
> I have a device connected with a client machine through COM1, now the
> client
> gets binary from it, then how can I transfer them to the server machine
> where the data will be stored in Microsoft SQL Server?
>
> I use MSComm control to help me get the data. The point is the data that
> serial-port device returns is 256 bytes long and is stored in byte
> array.The
> type of data's corresponding field in database is binary.What would I be
> careful of in order not to destroy the structure or content or format of
> the
> data? I am worried that the .net will treat it as the unicode string or
> something else and then will change something of the data.
>
>
>


 | 
Pages: 1
Prev: error code COOD1199
Next: LinQ. update column with auto generated value