[AccessD] What's wrong with this?

Darryl Collins darryl at whittleconsulting.com.au
Mon May 28 23:43:04 CDT 2012


Thanks Stuart, yes, you are 100% correct - it is the office version, and agree there is little advantage for most users in Office 64 bit - sorry for the misleading info Arthur - need another coffee it seems!
Cheers
Darryl

-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: Tuesday, 29 May 2012 12:55 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] What's wrong with this?

Actually, it doesn't matter whether you are using a 32 bit or a 64 bit OS.  The critical point is whether you are using 32 bit or 64 bit Office.

32bit Office on 64bit Windows still uses the Win32 API (through WOW64).

You only need conditional compilation if you are using Office x64.  (And there are no real advantages to Office x64 unless you need really big Excel spreadsheets.

--
Stuart


On 28 May 2012 at 22:45, Arthur Fuller wrote:

> Interesting. Frankly, that never occurred to me. Call me stoopid, that's
> ok. I've been called worse. Once I was called a one-legged mongrel dog from
> Mexico, but that's another story.
> 
> So currently I have two bootups, both Win7 64-bit, one loading Office 2007
> and the other loading Office 2003 + various SPs. I hate that re-install
> shyte that occurs if I try to load them both on one OS. Doesn't work! Hate
> that! Tong de Lawd fo multi-boot and VMs. Even though I am allegedly
> semi-retired, "I try to get out, but they keep dragging
> 
> On Mon, May 28, 2012 at 9:10 PM, Darryl Collins <
> darryl at whittleconsulting.com.au> wrote:
> 
> > Arthur,
> >
> > Just a reminder to check which Bit OS you are using.  If you are using 64
> > Bit windows you need to use a different API call than the 32 Bit version.
> >  This can cause the API to work fine on one system and fail on another.
> >
> > If you are unsure you can wrap the API call with a condition of "IF #VBA7
> > Then blah blah"
> >
> > Cheers
> > Darryl.
> >
> >
> >
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com [mailto:
> > accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
> > Sent: Tuesday, 29 May 2012 10:19 AM
> > To: Access Developers discussion and problem solving
> > Subject: [AccessD] What's wrong with this?
> >
> > I'm looking at an InsideAccess article on MSDN that's about FileOpen and
> > FileSaveAs. It's got some wonky spacing and punctuation, that I've tried to
> > clean up, but so far unsuccessfully.
> >
> > Here's what I have so far, and it won't permit it. I'm hoping someone can
> > either tell me what's wrong or maybe has this code in a form that is
> > considered acceptable. This is in a class module called CommonDialogAPI:
> > One thing that strikes me as odd is the lack of commas between items, but
> > maybe that's just the TYPE syntax. I don't know.
> >
> > <vba>
> > Private Type OPENFILENAME _
> >    lStructSize As Long _
> >    hwndOwner As Long _
> >    hInstance As Long _
> >    lpstrFilter As String _
> >    lpstrCustomFilter As String _
> >    nMaxCustFilter As Long _
> >    nFilterIndex As Long _
> >    lpstrFile As String _
> >    nMaxFile As Long _
> >    lpstrFileTitle As String _
> >    nMaxFileTitle As Long _
> >    lpstrInitialDir As String _
> >    lpstrTitle As String _
> >    Flags As Long _
> >    nFileOffset As Integer _
> >    nFileExtension As Integer _
> >    lpstrDefExt As String _
> >    lCustData As Long _
> >    lpfnHook As Long _
> >    lpTemplateName As String
> > End Type
> > </vba>
> >
> > Can you help? TIA.
> > --
> > Arthur
> > Cell: 647.710.1314
> >
> > Prediction is difficult, especially of the future.
> >  -- Niels Bohr
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> >
> >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> 
> 
> 
> -- 
> Arthur
> Cell: 647.710.1314
> 
> Prediction is difficult, especially of the future.
>   -- Niels Bohr
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 

--
Stuart McLachlan

Ph:    +675 340 4392 
Mob: +675 7100 2028
Web: http://www.lexacorp.com.pg

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





More information about the AccessD mailing list