2003==>2007: Safest Path?
in [Help]
|
Prev: printing a report without blank pages after a record in Access 2007
Next: printing a report without blank pages after a record in Access2007
From: (PeteCresswell) on 23 Jun 2010 15:10 We have an immediate need to convert an MS Access 2003 app and it's 2003 back end DB to 2007. We do not want or need any of 2007's functionality at this moment. I'm thinking maybe the safest path would be to use each of those DBs as 2003 .MDB files and just execute with 2007 - converting/testing at some later date when we're not under the gun any more. Does this work for anybody? Or should I bite the bullet and convert/test now rather than later? -- PeteCresswell
From: Bob Alston on 23 Jun 2010 15:13 (PeteCresswell) wrote: > We have an immediate need to convert an MS Access 2003 app and > it's 2003 back end DB to 2007. > > We do not want or need any of 2007's functionality at this > moment. > > I'm thinking maybe the safest path would be to use each of those > DBs as 2003 .MDB files and just execute with 2007 - > converting/testing at some later date when we're not under the > gun any more. > > Does this work for anybody? Or should I bite the bullet and > convert/test now rather than later? Why????????
From: (PeteCresswell) on 23 Jun 2010 16:06 Per Bob Alston: >(PeteCresswell) wrote: >> We have an immediate need to convert an MS Access 2003 app and >> it's 2003 back end DB to 2007. >> >> We do not want or need any of 2007's functionality at this >> moment. >> >> I'm thinking maybe the safest path would be to use each of those >> DBs as 2003 .MDB files and just execute with 2007 - >> converting/testing at some later date when we're not under the >> gun any more. >> >> Does this work for anybody? Or should I bite the bullet and >> convert/test now rather than later? > > >Why???????? Why what? Convert or run as 2003? -- PeteCresswell
From: Douglas J. Steele on 23 Jun 2010 17:28 You should be fine simply using the existing MDB files. Check http://www.allenbrowne.com/Access2007.html at Allen Browne's site for more information when you are ready to convert. -- Doug Steele, Microsoft Access MVP http://www.AccessMVP.com/DJSteele/AccessIndex.html Co-author: "Access 2010 Solutions", published by Wiley (no private e-mails, please) "(PeteCresswell)" <x(a)y.Invalid> wrote in message news:nrm426tnmt94lkki9prvdeae632vs9t7kk(a)4ax.com... > We have an immediate need to convert an MS Access 2003 app and > it's 2003 back end DB to 2007. > > We do not want or need any of 2007's functionality at this > moment. > > I'm thinking maybe the safest path would be to use each of those > DBs as 2003 .MDB files and just execute with 2007 - > converting/testing at some later date when we're not under the > gun any more. > > Does this work for anybody? Or should I bite the bullet and > convert/test now rather than later? > -- > PeteCresswell
From: Arvin Meyer on 24 Jun 2010 12:49
I would not convert at all. Just leave it alone. If you do not need later version features, there is no reason to "upgrade" the app. -- Arvin Meyer, MCP, MVP http://www.datastrat.com http://www.accessmvp.com http://www.mvps.org/access Co-author: "Access 2010 Solutions", published by Wiley "(PeteCresswell)" <x(a)y.Invalid> wrote in message news:nrm426tnmt94lkki9prvdeae632vs9t7kk(a)4ax.com... > We have an immediate need to convert an MS Access 2003 app and > it's 2003 back end DB to 2007. > > We do not want or need any of 2007's functionality at this > moment. > > I'm thinking maybe the safest path would be to use each of those > DBs as 2003 .MDB files and just execute with 2007 - > converting/testing at some later date when we're not under the > gun any more. > > Does this work for anybody? Or should I bite the bullet and > convert/test now rather than later? > -- > PeteCresswell |