[AccessD] Windows 7

Hey Rocky
No a test bed is not an option at the moment.  I could get them to set 
the compatability mode for Access2003 or rewrite the code for the 
commondialog and not use an activex control. But I am just wondering how 
this is going to affect other standalone applications I have designed in 
Access2003 for other clients.

Rocky Smolin wrote:

>I put W7 on my backup box so I don't do much Access over there.  But what I
>have done - so far no problems.  Do you have a spare box you could put W7 on
>and use for a test bed?
>
>Rocky
> 
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Tony Septav
>Sent: Friday, January 14, 2011 6:11 AM
>To: Access Developers discussion and problem solving
>Subject: [AccessD] Windows 7
>
>Hey All
>I have an Access2003 program (MDE) used by a client, they have upgraded
>their machines to Windows 7  and now they get the dreaded  "The OpenForm
>action was cancelled" when they click the button on the main menu for one
>option (the others all work fine). The only thing this form has that the
>others don't is a CommonDialog control.  I haven't as yet had them check for
>missing references (the office doesn't open until 8AM, I may have to send
>them the MDB to check).  They startup the program with their version of
>Access2003.  In trying to research the cause of this problem,  I am seeing
>that  Access2003 can develop some problems when running under Windows 7.
>Have any of you run into other  problems?
>
>Thanks
>Tony
> 
>--
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com
>
>  
>