Access 97/2003/SQL Server Express
Currently we have an Access97 database - we were rewriting it in Access 2003. Once everything was tested on 2003, we were going to leave the frontend programs in 2003 and put the data in SQL Server Express. Unfortunately, since Microsoft is dropping Access 2003; it is harder to get the upgrades so my question is this: What would happen if we run Access97 as the front end with SQL Server Express as the back end? Are we going to run into performance issues? Or is there another solution I am not thinking of? We are a small office with a limited budget but a large project is quickly approaching. BTW, we are running Windows XP 2.4Ghz systems, 512mb RAM on a Windows 2003 Server. Thank you
ASKER
The reason I am saying that is because I checked with three of our suppliers and they were sold out of Access 2003 upgrades and were not going to get anymore. My concern is that we pick up a couple of copies now off of a third party site, I question whether or not we can get them in the future. I totally understand 2003 is more supported than 97 and I don't want to move backwards - just looking for alternatives. Thanks.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That is one thing that crossed my mind briefly - I used Access97 Developer Edition a lot in a previous job but was thinking they quit making it for some reason.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
the runtime for 2007 and the deployment packager will be free, I have seen M$ saying it will be ready next month.
<<the runtime for 2007 and the deployment packager will be free,>>
I'd be very suprised at that. They have never done that before.
JimD
I'd be very suprised at that. They have never done that before.
JimD
ASKER
Yes, I seen that on the website - Microsoft giving something away for free...hmm, whats the world coming to :)
<<Yes, I seen that on the website - Microsoft giving something away for free...hmm, whats the world coming to :)>>
Can you post a link?
JimD
Can you post a link?
JimD
Maybe you guys are thinking of this:
Visual Studio 2005 Tools for Office Second Edition
http://msdn2.microsoft.com/en-us/office/aa905543.aspx
This does not include the license to distribute the Access runtime nor does it have any of the tools for Access. Also the download for this is free, but it's free only if already own a license for Visual Studio 2005 Tools for Office or for Visual Studio Professional and above (either standalone versions or via an MSDN Premium or Professional subscription).
JimD.
Visual Studio 2005 Tools for Office Second Edition
http://msdn2.microsoft.com/en-us/office/aa905543.aspx
This does not include the license to distribute the Access runtime nor does it have any of the tools for Access. Also the download for this is free, but it's free only if already own a license for Visual Studio 2005 Tools for Office or for Visual Studio Professional and above (either standalone versions or via an MSDN Premium or Professional subscription).
JimD.
nah ... clint covington (from M$) posted it on his blog ... let me find it ...
here it is ...
http://blogs.msdn.com/clintcovington/archive/2007/01/30/the-runtime-and-developer-extensions-will-be-free.aspx
and the runtime deploy will create the "trusted" key in the registry ...
http://blogs.msdn.com/clintcovington/archive/2007/02/21/my-favorite-access-keyboard-commands.aspx
http://blogs.msdn.com/clintcovington/archive/2007/01/30/the-runtime-and-developer-extensions-will-be-free.aspx
and the runtime deploy will create the "trusted" key in the registry ...
http://blogs.msdn.com/clintcovington/archive/2007/02/21/my-favorite-access-keyboard-commands.aspx
the real M$ page is referenced in his blog ...
http://msdn2.microsoft.com/en-us/office/bb229700.aspx
http://msdn2.microsoft.com/en-us/office/bb229700.aspx
Wow, that's a real shock; almost wish it were not so. Access has always gotten a bad rap because so many "developers" simply don't know how and when to use it properly. Sounds like it's about to get worse<g>.
Of course that means a lot more work to as well to clean up all the messes....
I've been almost full-time on one client like that for the past three years<g>.
JimD
<rant>
personally I would agree it is a mistake but I *think* this really has more to do with M$ trying to buy a bit of goodwill from all the gripes *real* Access developers have with 2007. Most responses seem to be positive ... kind of like when VB.Net developers compalined about so much, M$ bought a third party refactoring component and included it in VB.Net ... "see, we are listening" but silently, while we are listening we are not chaning the things you don't like we are just distracting you with a shiny penny ... works every time.
</rant>
personally I would agree it is a mistake but I *think* this really has more to do with M$ trying to buy a bit of goodwill from all the gripes *real* Access developers have with 2007. Most responses seem to be positive ... kind of like when VB.Net developers compalined about so much, M$ bought a third party refactoring component and included it in VB.Net ... "see, we are listening" but silently, while we are listening we are not chaning the things you don't like we are just distracting you with a shiny penny ... works every time.
</rant>
I don't understand the decision between Access 97 and 2003. Certainly 97 at this point is far less supported then 2003. Microsoft has only "dropped" 2003 in the sense that 2007 has been released; but it will still be supported for security and any major bug fixes.
I can't see why you would not want to use 2003.
JimD