[AccessD] Issues with running applications in 64 bit version ofOffice

<<I'm just trying to strategize on how to make the code transparent to
2003,2007,2010, 32 and 64 bit.
How to handle 2003 if VBA7 and WIN64 don't exist ?>>

I think I mis-lead you when I said no.  They don't exist, but if you use
them in code, they are just ignored.  So this:

	#If VBA7 Then
	' PTRSafe used
      #ELSE
      ' no PTRSafe used.
	#End If

Is perfectly valid and will compile in 2003 and execute correctly.

Jim.


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms
Sent: Monday, January 30, 2012 11:36 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Issues with running applications in 64 bit version
ofOffice

I'm just trying to strategize on how to make the code transparent to
2003,2007,2010, 32 and 64 bit.
How to handle 2003 if VBA7 and WIN64 don't exist ?
I can't set my own VBA7 directive as that will override the internal one.
Getting the version doesn't help, that's at run-time.
I need make a POST2003VERSION directive...I believe....and just change that
one line of code to make it work with all releases.
#Const POST2003VERSION = False ' Change only this one line of code to
support older releases
#If POST2003VERSION Then
	#If VBA7 Then
	' LongPtr, PtrSage declares etc. goes here
	#End If
#Else
	' standard declares go here
#End If


>
> <<Does 2003 have a VBA7 directive already declared internally ?>>
>   No.


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com