that was files by the way, i've mistakenly typed it as filr!
Could have been some new kind of file-type I never heard of
Member 12901689 wrote:
Yeah youre right i should just stick to the lessons rather than try to do new things,
Not everyone is here to learn; some people get impatient if they don't make any progress. If you change your username to something that I can remember, then I'll try to be answering with a bit more detail next time
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
In a vb.net 2010 application, I have the following code setup so far:
Dim _dtEmailaddress As DataTable = SelectEmailAddress(_dtPersonID(0)("SPA_PersonID"))
Dim _email As String = String.Empty
If _dtEmailaddress.Rows.Count > 0 Then
If IsDBNull((_dtEmailaddress(0)("email"))) Then
_letter = _letter.Replace("&SPA_EMAIL.EVAL", "")
_letter = _letter.Replace("&SPA_EMAIL.EVAL", _dtEmailaddress(0)("email"))
I need to be able to check for email addresses that end with '@opd.org' in the reference called _dtEmailaddress(0)("email").
Thus can you show me the vb.net code so I would know how to use only email addresses that end with '@opd.org'?
I am working with a piece of VB6 code that reads data from an instrument through the USB port.
The instrument uses an FTID USB chip and the data is read by the host byte by byte from the USB bus using a driver supplied by FTID.
Each data byte is returned as a string character and then converted using the function Asc(string).
The problem is that on Windows 10 machines running chinese, the data returned is corrupted.
I think this may have something to do with the longer (2 bytes per character instead of one) character coding used for chinese but I have not been able to understand the issue.
The issue of presenting characters in the correct format depends on how they are encoded and what font you use. The first thing you need to identify is exactly what, and what form, is the data that is being read from the chip.
Thanks for your reply. The code reads data (not text) from eeprom in the instrument. The FTDI driver (which I have no control over) returns each byte read from the USB bus as a string character.
That is why I use Asc(string) to get me the byte value that I need.
The problem, for example:
instead of reading 0 22 129 0 22
in the chinese PC I get 63 63 63 0 0
Well, the code could not be simpler. Just one line of code. The rest is done by the FTDI library routine that reads the USB data and passes it as a string. It all works fine in all systems we tested except Win10 running the chinese version.
But thank you for taking the time to comment.