Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.databases.ms-access > #9010 > unrolled thread

Porting 2007 App To Run Under 2010?

Back to article view | Back to comp.databases.ms-access

Contents

  Porting 2007 App To Run Under 2010? "(PeteCresswell)" <x@y.Invalid> - 2014-02-13 08:08 -0500
    Re: Porting 2007 App To Run Under 2010? "Albert D. Kallal" <PleaseNOSpamkallal@msn.com> - 2014-02-13 13:11 -0700
    Re: Porting 2007 App To Run Under 2010? PW <emailaddyinsig@ifIremember.com> - 2014-02-14 10:56 -0700
      Re: Porting 2007 App To Run Under 2010? "(PeteCresswell)" <x@y.Invalid> - 2014-02-14 14:52 -0500
        Re: Porting 2007 App To Run Under 2010? "Access Developer" <accdevel@gmail.com> - 2014-02-14 14:04 -0600
          Re: Porting 2007 App To Run Under 2010? "(PeteCresswell)" <x@y.Invalid> - 2014-02-14 17:31 -0500
        Re: Porting 2007 App To Run Under 2010? "Albert D. Kallal" <PleaseNOSpamkallal@msn.com> - 2014-02-16 12:50 -0700
          Re: Porting 2007 App To Run Under 2010? "(PeteCresswell)" <x@y.Invalid> - 2014-02-16 20:51 -0500
    Re: Porting 2007 App To Run Under 2010? CDMAPoster@fortunejames.com - 2014-03-25 13:03 -0700

#9010 — Porting 2007 App To Run Under 2010?

I have an app, originally written under 2003 and then modified to run
under 2007.

Now the client's IT div is pushing out Windows 7 and, along with it,
Office 2010 (32-bit).

Should I be looking for any problems?   Or can I hope for a transparent
port?
-- 
Pete Cresswell

[toc] | [next] | [standalone]

#9013

"(PeteCresswell)"  wrote in message 
news:7qgpf9h9eif27p2mj4rkv2f8iukm8q2gmu@4ax.com...

I have an app, originally written under 2003 and then modified to run
under 2007.

Now the client's IT div is pushing out Windows 7 and, along with it,
Office 2010 (32-bit).

Should I be looking for any problems?   Or can I hope for a transparent
port?
-- 
Pete Cresswell

===

Hum, no more problems then say upgrading in the old days from 2002 to 2003. 
They are very simular - so things like broken refercnes etc and any typical 
problem that crops up can and will.

However from a practical point of view, all should be find and I cannot 
think of any changes that would cause any issues.

-- 
Albert D. Kallal  (Access MVP)
Edmonton, Alberta Canada
PleaseNoSpam_kallal@msn.com 

[toc] | [prev] | [next] | [standalone]

#9017

On Thu, 13 Feb 2014 08:08:07 -0500, "(PeteCresswell)" <x@y.Invalid>
wrote:

>I have an app, originally written under 2003 and then modified to run
>under 2007.
>
>Now the client's IT div is pushing out Windows 7 and, along with it,
>Office 2010 (32-bit).
>
>Should I be looking for any problems?   Or can I hope for a transparent
>port?

I've had no problems importing Access 2003 tables and forms, reports,
etc..  into Access 2013.  I can't remember if I used the External Data
or Database Tools ribbon.  But I think you will want to select the
Import option.

It also worked going from 79 -> 2003.

-paulw

[toc] | [prev] | [next] | [standalone]

#9018

Per PW:
>I've had no problems importing Access 2003 tables and forms, reports,
>etc..  into Access 2013.  I can't remember if I used the External Data
>or Database Tools ribbon.  But I think you will want to select the
>Import option.
>
>It also worked going from 79 -> 2003.

Does anybody know if the same gotcha applies as with 2003 and 2007 where
2003 could not be installed once 2007 was installed?

I'm trying to cover my bases in case 2010 does not work out for some
unforeseen reason.
-- 
Pete Cresswell

[toc] | [prev] | [next] | [standalone]

#9019

The advice I see, mostly, is to install a virtual machine, and install 
Access 2003 on that, so that "strictly speaking", they aren't installed / 
running on the same system.

-- 
Larry Linson
  Microsoft Office Access MVP
  Co-Author, Microsoft Access Small Business Solutions, Wiley 2010

"(PeteCresswell)" <x@y.Invalid> wrote in message 
news:oussf9d597pdst23n6f87r3jvi6qkmgnae@4ax.com...
> Per PW:
>>I've had no problems importing Access 2003 tables and forms, reports,
>>etc..  into Access 2013.  I can't remember if I used the External Data
>>or Database Tools ribbon.  But I think you will want to select the
>>Import option.
>>
>>It also worked going from 79 -> 2003.
>
> Does anybody know if the same gotcha applies as with 2003 and 2007 where
> 2003 could not be installed once 2007 was installed?
>
> I'm trying to cover my bases in case 2010 does not work out for some
> unforeseen reason.
> -- 
> Pete Cresswell 

[toc] | [prev] | [next] | [standalone]

#9020

Per Access Developer:
>The advice I see, mostly, is to install a virtual machine, and install 
>Access 2003 on that, so that "strictly speaking", they aren't installed / 
>running on the same system.

Even if I knew what a virtual machine was, that's not going to fly on
this guy's laptop.   It's got to be simple and transparent.

I think I'll just tell IT to be sure to install Access 2007 before they
install Office 210.  Then I'm covered and we can always remove 2007 once
2010 is fully shaken out.
-- 
Pete Cresswell

[toc] | [prev] | [next] | [standalone]

#9025

"(PeteCresswell)"  wrote in message 
news:oussf9d597pdst23n6f87r3jvi6qkmgnae@4ax.com...

>Does anybody know if the same gotcha applies as with 2003 and 2007 where
>2003 could not be installed once 2007 was installed?

The above is not the case. it was always "recommend" to install in 
increasing version order, but NOT a requirement.

Access 97, 2000, 2003, 2007, and 2010 can all reside quite happy on the SAME 
computer, say a brand new win 7 x64 box.

I am not quite sure "WHEN" the recommend of installing in order changed from 
being a "good" idea to that of something that does not work.

In fact even in older days on machines that had access 97, when we upgraded 
them to access 2003, trying to "un-install" Access 97 proved to be such a 
HUGE mess and issues, that we simply adopted the practice of NOT removing 
the previous version - just leave it alone - don't even touch it at all!  - 
hard drives are cheap and messing around for 30 minutes will cost more in 
support time for a machine that likely to be tossed out in a few years.

So I don't even recommend trying to mess, touch, waste time on worrying 
about "previous" editions on that computer. Install the latest version you 
need and that's it. Don't even try to un-install previous - as many things 
can mess up during a un-install as an install!

And for developers? Yes, we recommend (if not live and die) by using some 
kind of virtual computing. However virtual computing is not a "general" 
solution for the deployment side of things

Best regards,

-- 
Albert D. Kallal  (Access MVP)
Edmonton, Alberta Canada
PleaseNoSpam_kallal@msn.com 

[toc] | [prev] | [next] | [standalone]

#9026

Per Albert D. Kallal:
>I am not quite sure "WHEN" the recommend of installing in order changed from 
>being a "good" idea to that of something that does not work.

Maybe some time after Yours Truly got burned when he tried to install
2003 on top of 2007..... -)   Trust me, it doesn't work.
-- 
Pete Cresswell

[toc] | [prev] | [next] | [standalone]

#9196

On Thursday, February 13, 2014 8:08:07 AM UTC-5, (PeteCresswell) wrote:
> I have an app, originally written under 2003 and then modified to run
> 
> under 2007.
> 
> 
> 
> Now the client's IT div is pushing out Windows 7 and, along with it,
> 
> Office 2010 (32-bit).
> 
> 
> 
> Should I be looking for any problems?   Or can I hope for a transparent
> 
> port?
> 
> -- 
> 
> Pete Cresswell

On a domain with a mix of 32 and 64-bit OS computers running various 32 or 64-bit versions of Access (Note: A 64-bit OS computer can have a 32-bit version of Access installed), API functions should be changed to use constants such as vba7 and win64 to provide conditional compilation of PtrSafe versions of the API declarations.  Those can be made to work for most situations, but IIRC, not all combinations - some installations will still compile error when they see the PtrSafe declarations despite the conditional compiler directives and require extra care.  You don't have that problem because your customer isn't letting older versions of Access and 32-bit OS's hang around.  The PtrSave declaration was the biggest change I encountered.

See:
http://msdn.microsoft.com/en-us/library/ee691831.aspx

James A. Fortune
CDMAPoster@FortuneJames.com

Still lovin' Access

[toc] | [prev] | [standalone]

Back to top | Article view | comp.databases.ms-access

csiph-web