S
S
I have read last year's thread on the future of Access but have a few
questions about where Microsoft are going with Access as I need to make
decisions on what to spend my learning time on. I currently develop highly
automated processes using VBA and SQL in Access 2000/2003 for users with full
versions of Access. These users are non-comercial which tends to mean there
equipment is at the cheaper end and their software is not the latest thing.
Are there plans to take Access down the .Net road?
What is the future of VBA, whould it be better to change to VB for future
work? Presumable this would involve deploying .Net.
For new work I am wondering whether it is would be useful to have the
developer's extension which is now packaged with VSTO for the licences to
distribute a run-time version of Access. A few things put me off this:
Developers who only use the Access bit have had to upgrade from VSTO 2003 to
2005 just to get the licences when the Access bit has not changed. Is this
going to keep happening to Developers who are not producing .Net products?
I have seen critisms of the package wizard and I cannot findout if it is
able to check the path of msaccess.exe and create the type of shortcut that
specifies the location of the workgroup file for a secured database.
Any help would be apreciated.
questions about where Microsoft are going with Access as I need to make
decisions on what to spend my learning time on. I currently develop highly
automated processes using VBA and SQL in Access 2000/2003 for users with full
versions of Access. These users are non-comercial which tends to mean there
equipment is at the cheaper end and their software is not the latest thing.
Are there plans to take Access down the .Net road?
What is the future of VBA, whould it be better to change to VB for future
work? Presumable this would involve deploying .Net.
For new work I am wondering whether it is would be useful to have the
developer's extension which is now packaged with VSTO for the licences to
distribute a run-time version of Access. A few things put me off this:
Developers who only use the Access bit have had to upgrade from VSTO 2003 to
2005 just to get the licences when the Access bit has not changed. Is this
going to keep happening to Developers who are not producing .Net products?
I have seen critisms of the package wizard and I cannot findout if it is
able to check the path of msaccess.exe and create the type of shortcut that
specifies the location of the workgroup file for a secured database.
Any help would be apreciated.