variables in 64 bit OS
in [Visual Basic]
|
Prev: Read/ Write file header
Next: Localized Date
From: Claire on 3 May 2010 14:29 Hello, I wrote the code in late 90's and some of my global variables are declared as Byte. My question is: Should I convert all those variables to Long as now we are dealing more and more with 64 bit Windows, or it does not matter? I do not want to run into compatibility problem. Thanks, Claire
From: David Kerber on 3 May 2010 15:16 In article <OSScK6u6KHA.5848(a)TK2MSFTNGP06.phx.gbl>, replyto(a)fra says... > > Hello, > I wrote the code in late 90's and some of my global variables are > declared as Byte. > My question is: > Should I convert all those variables to Long as now we are dealing more and > more with 64 bit Windows, or it does not matter? > I do not want to run into compatibility problem. > Thanks, > Claire As long as your programming language supports a given variable type on the platform, you will be fine. D
From: MikeD on 3 May 2010 15:21 "Claire" <replyto(a)fra> wrote in message news:OSScK6u6KHA.5848(a)TK2MSFTNGP06.phx.gbl... > Hello, > I wrote the code in late 90's and some of my global variables are declared as Byte. > My question is: > Should I convert all those variables to Long as now we are dealing more and more with 64 bit Windows, or it does not matter? > I do not want to run into compatibility problem. > Thanks, Well you wouldn't change Byte variables to Long anyway. You *might* change Integer variables to Long, but that was really more with going from 16 bit development to 32 bit development. The apps you create with VB6 are 32 bit apps and when run on a 64 bit OS, run in the 32 bit sub-system (called WOW64). So what I'm saying is you should not have to change anything in your 32 bit VB6 apps for them to run on a 64 bit version of Windows. Running into compatibility problems is something else entirely. -- Mike
From: Claire on 3 May 2010 18:34 "David Kerber" <ns_dkerber(a)ns_warrenrogersassociates.com> wrote in message news:MPG.2648eb12da4a83fc9896fd(a)news.onecommunications.net... > In article <OSScK6u6KHA.5848(a)TK2MSFTNGP06.phx.gbl>, replyto(a)fra says... >> >> Hello, >> I wrote the code in late 90's and some of my global variables >> are >> declared as Byte. >> My question is: >> Should I convert all those variables to Long as now we are dealing more >> and >> more with 64 bit Windows, or it does not matter? >> I do not want to run into compatibility problem. >> Thanks, >> Claire > > As long as your programming language supports a given variable type on > the platform, you will be fine. > > D I thought it is classic vbasic programming forum only.
From: Claire on 3 May 2010 18:35
"MikeD" <nobody(a)nowhere.edu> wrote in message news:%23V3PiXv6KHA.5708(a)TK2MSFTNGP02.phx.gbl... > > "Claire" <replyto(a)fra> wrote in message > news:OSScK6u6KHA.5848(a)TK2MSFTNGP06.phx.gbl... >> Hello, >> I wrote the code in late 90's and some of my global variables >> are declared as Byte. >> My question is: >> Should I convert all those variables to Long as now we are dealing more >> and more with 64 bit Windows, or it does not matter? >> I do not want to run into compatibility problem. >> Thanks, > > > Well you wouldn't change Byte variables to Long anyway. You *might* > change Integer variables to Long, but that was really more with going from > 16 bit development to 32 bit development. > > The apps you create with VB6 are 32 bit apps and when run on a 64 bit OS, > run in the 32 bit sub-system (called WOW64). > > So what I'm saying is you should not have to change anything in your 32 > bit VB6 apps for them to run on a 64 bit version of Windows. > > Running into compatibility problems is something else entirely. > > > -- > Mike > Mike, I do have also some variables declared as Integer. Should I change those? Claire |