01-16-2006 06:37 AM
01-16-2006 06:41 AM
I forgot to say that I use LV 7.1 and an Access DataBase.
Thank you!
01-16-2006 06:48 AM - edited 01-16-2006 06:48 AM
Message Edited by David Crawford on 01-16-2006 06:49 AM
01-16-2006 06:53 AM
01-16-2006 06:54 AM
I should have said that this was part of a SQL statement for the DB Tool Execute Query.vi. I don't know if this would make a difference with DB Tools Select Data.vi.
David
01-16-2006 12:32 PM
Hello becktho,
I modified a little your VI in order to attach it to my VI and it works fine. Thank you very much!
Could you explain me a little more why it's impossible to enter "#" into a string?
What should I do in order to have a string control where I could type "#27/10/2003#"?
Does anyone know this?
Thank you very much!
Nuria
01-17-2006 12:24 AM
01-17-2006 09:01 AM - edited 01-17-2006 09:01 AM
This is a limitation of your Windows locale not of the LabVIEW string control. With keyboards that to not need multi-finger keypresses to enter the # character there is absolutely no problem with this. Windows applications translate accelerators (menu shortcuts) first before interpreting the key combination so you end up with a catch 22 here. Since LabVIEW has a menu shortcut Ctrl-# Windows does not know better as to pass this shortcut to LabVIEW instead of translating the locale keyboard translation.
@leiabcn wrote:Hello becktho,
I modified a little your VI in order to attach it to my VI and it works fine. Thank you very much!
Could you explain me a little more why it's impossible to enter "#" into a string?
What should I do in order to have a string control where I could type "#27/10/2003#"?
Does anyone know this?
Thank you very much!
Message Edited by rolfk on 01-17-2006 04:11 PM