If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#11
|
|||
|
|||
Access 2002 vs. 2003
FYI, found this link:
http://office.microsoft.com/en-us/as...714971033.aspx . Has the same info, but with some nice screen shots. N "Albert D.Kallal" wrote in message ... We are also looking to do a fair amount of redevelopment of our application, and I want to do it in 2003. I also like 2003. Things like themed controls make the software look a LOT better. here is some screen shots of what I mean http://www.members.shaw.ca/AlbertKal...icles/Grid.htm and http://www.members.shaw.ca/AlbertKal...heme/index.htm Am I right for insisting on Access 2003 over 2002, or is there not that much of a difference? If there is a significant difference, what can I say in support of getting licenses for Access 2003? No, you are not. I can't see any good reason, or argument to upgrade here. The only reason would be that you "like" a2003 better..... There is little, if any changes in terms of support for sql server....so, no, there is no big real argument here that I can make a case. However, see below for a2003 features (this is a reposted message) Also, here is a fabulous post by MVP John Viescas on this very subject late last year. (This was comparing Access 2003 to 2002). They didn't make any major changes. Here's a summary: View information on object dependencies In Microsoft Office Access 2003, you can view information on dependencies between database objects. Viewing a list of objects that use a specific object helps maintain a database over time and avoid errors related to missing record sources. For example, the Quarterly Orders query in the Sales database is no longer needed, but before deleting it, you might want to find out which other objects in the database use the query. Then, you could either change the record source of the dependent objects, or delete them, before deleting the Quarterly Orders query. Viewing a complete list of dependent objects helps you save time and minimize errors. In addition to viewing the list of objects that are bound to a selected object, you can also view the objects that are being used by the selected object. Macros, modules, and data access pages are not searched for dependencies. Access projects do not support this feature. Error checking in forms and reports In Microsoft Office Access 2003, you can enable automatic error checking for common errors in forms and reports. Error checking points out errors, such as two controls using the same keyboard shortcut, and the width of a report being greater than the page it will be printed on. Enabling error checking helps you identify errors and correct them. Propagating field properties In previous versions of Microsoft Access, whenever you modified a field's inherited property, you had to manually modify the property of the corresponding control in each of the forms and reports. Now, when you modify an inherited field property in Table design view, Access displays an option to update the property of all or some controls that are bound to the field. Smart tags In Microsoft Office Access 2003, you can use the SmartTags property to add a smart tag to any field in a table, query, form, report, or data access page in a database. Back up a database or project You can back up the current database or project before making major changes to it. The backup will be saved in the default backup location, or in the current folder. To restore a database, go to the location of the backup, rename the file, and open it in Access. Windows XP theme support The Microsoft Windows XP operating system offers you several themes. If you have chosen a theme other than the default, Access will apply the chosen theme to views, dialog boxes, and controls. You can prevent form controls from inheriting themes from the operating system by setting an option on the database or project. Improved sorting in controls You can now specify the ascending or descending sort order of up to four fields in the List Box and Combo Box Wizards in forms and reports, and the Lookup Wizard in an Access database. The sort page added to these wizards looks and behaves like the sort page in the Report Wizard. Autocorrect options In Microsoft Office Access 2003, you have more control over the behavior of the AutoCorrect feature. The AutoCorrect Options button appears near text that was automatically corrected. If you find on occasion that you don't want text to be corrected, you can undo a correction or turn AutoCorrect options on or off by clicking the button and making a selection. Enhanced font capabilities in SQL views In the SQL and query Design views of a query in both a Microsoft Access database and Microsoft Access project, you can now change the font and font size of the text by using the Query design font option added to the Tables/Queries tab of the Options dialog box under the Tools menu. These settings apply to all databases and work with the high-contrast and other accessibility settings of your computer. Context-based Help in SQL view In the SQL view of a query in a Microsoft Access database, you can now get help specific to Jet SQL keywords, VBA functions, and Access functions. Simply press F1 to bring up the help that corresponds to the text near the cursor. You can also search the Jet SQL and VBA function reference topics. Importing, exporting, and linking Importing, exporting, and linking to a Microsoft Windows SharePoint Services list from Access You can perform the following operations with a Windows SharePoint Services list: ?Export the contents of a table or a query to a list. ?Import the contents of a list into a table. ?Link a table to a list. Exporting and linking to Access data from Windows SharePoint Services You can now export a list in its Datasheet view from Windows SharePoint Services to a static table or to a linked table in Access. When you export to a static table, you create a table in Access. You can then view and make changes to the table independent of the original list in Windows SharePoint Services. Similarly, you can change the list in Windows SharePoint Services, and that will not affect the table in Access. When you export to a linked table, you create a table in Access and establish a dynamic link between the table and the list such that changes to the table are reflected in the list, and changes to the list are reflected in the table as well. Make a local table from a linked table In Microsoft Office Access 2003, you can make a local copy of the structure or data and structure contained in a linked table. XML support With the enhanced XML support in Microsoft Office Access 2003, you can specify a transform file when you import data from or export data to XML. The transform is then applied automatically. When you import XML data, the transform is applied to the data as soon as the data is imported, before any new table is created or an existing one is appended to. When you export data to XML, the transform is applied following the export operation. Often times a database contains lookup values that are stored in another database. You can now include these related tables when exporting. You can also include any predefined filter or sort order for an object when exporting the object. Security enhancements Macro Security Microsoft Office Access 2003 allows you to protect against potentially unsafe Visual Basic for Applications (VBA) code by setting the macro security level. You can set the security level so that you are prompted every time that you open a database containing VBA code, or you can automatically block databases that are from unknown sources. Additionally, Access uses Microsoft Authenticode technology to enable you to digitally sign a macro project by using a digital certificate. The certificate used to create this signature confirms that the macro originated from the signer, and the signature confirms that it has not been altered. When you set the macro security level, you can run macros based on whether they are digitally signed by a developer on your list of trusted sources. Block Potentially Unsafe Functions Access utilizes the Microsoft Jet Expression Service enhanced sandbox mode to block potentially unsafe functions from being used in expressions. |
#12
|
|||
|
|||
Access 2002 vs. 2003
Thanks for the samples regarding themed controls. Not sure what the
difference would be between using themed controls and just applying a particular background shading manually. The only differences I saw were the background shading and the rounded corners on buttons. Is there something else. (By the way, the second set of screen shots DO look much better. Very nice!) Neil "Albert D.Kallal" wrote in message ... We are also looking to do a fair amount of redevelopment of our application, and I want to do it in 2003. I also like 2003. Things like themed controls make the software look a LOT better. here is some screen shots of what I mean http://www.members.shaw.ca/AlbertKal...icles/Grid.htm and http://www.members.shaw.ca/AlbertKal...heme/index.htm Am I right for insisting on Access 2003 over 2002, or is there not that much of a difference? If there is a significant difference, what can I say in support of getting licenses for Access 2003? No, you are not. I can't see any good reason, or argument to upgrade here. The only reason would be that you "like" a2003 better..... There is little, if any changes in terms of support for sql server....so, no, there is no big real argument here that I can make a case. However, see below for a2003 features (this is a reposted message) Also, here is a fabulous post by MVP John Viescas on this very subject late last year. (This was comparing Access 2003 to 2002). They didn't make any major changes. Here's a summary: View information on object dependencies In Microsoft Office Access 2003, you can view information on dependencies between database objects. Viewing a list of objects that use a specific object helps maintain a database over time and avoid errors related to missing record sources. For example, the Quarterly Orders query in the Sales database is no longer needed, but before deleting it, you might want to find out which other objects in the database use the query. Then, you could either change the record source of the dependent objects, or delete them, before deleting the Quarterly Orders query. Viewing a complete list of dependent objects helps you save time and minimize errors. In addition to viewing the list of objects that are bound to a selected object, you can also view the objects that are being used by the selected object. Macros, modules, and data access pages are not searched for dependencies. Access projects do not support this feature. Error checking in forms and reports In Microsoft Office Access 2003, you can enable automatic error checking for common errors in forms and reports. Error checking points out errors, such as two controls using the same keyboard shortcut, and the width of a report being greater than the page it will be printed on. Enabling error checking helps you identify errors and correct them. Propagating field properties In previous versions of Microsoft Access, whenever you modified a field's inherited property, you had to manually modify the property of the corresponding control in each of the forms and reports. Now, when you modify an inherited field property in Table design view, Access displays an option to update the property of all or some controls that are bound to the field. Smart tags In Microsoft Office Access 2003, you can use the SmartTags property to add a smart tag to any field in a table, query, form, report, or data access page in a database. Back up a database or project You can back up the current database or project before making major changes to it. The backup will be saved in the default backup location, or in the current folder. To restore a database, go to the location of the backup, rename the file, and open it in Access. Windows XP theme support The Microsoft Windows XP operating system offers you several themes. If you have chosen a theme other than the default, Access will apply the chosen theme to views, dialog boxes, and controls. You can prevent form controls from inheriting themes from the operating system by setting an option on the database or project. Improved sorting in controls You can now specify the ascending or descending sort order of up to four fields in the List Box and Combo Box Wizards in forms and reports, and the Lookup Wizard in an Access database. The sort page added to these wizards looks and behaves like the sort page in the Report Wizard. Autocorrect options In Microsoft Office Access 2003, you have more control over the behavior of the AutoCorrect feature. The AutoCorrect Options button appears near text that was automatically corrected. If you find on occasion that you don't want text to be corrected, you can undo a correction or turn AutoCorrect options on or off by clicking the button and making a selection. Enhanced font capabilities in SQL views In the SQL and query Design views of a query in both a Microsoft Access database and Microsoft Access project, you can now change the font and font size of the text by using the Query design font option added to the Tables/Queries tab of the Options dialog box under the Tools menu. These settings apply to all databases and work with the high-contrast and other accessibility settings of your computer. Context-based Help in SQL view In the SQL view of a query in a Microsoft Access database, you can now get help specific to Jet SQL keywords, VBA functions, and Access functions. Simply press F1 to bring up the help that corresponds to the text near the cursor. You can also search the Jet SQL and VBA function reference topics. Importing, exporting, and linking Importing, exporting, and linking to a Microsoft Windows SharePoint Services list from Access You can perform the following operations with a Windows SharePoint Services list: ?Export the contents of a table or a query to a list. ?Import the contents of a list into a table. ?Link a table to a list. Exporting and linking to Access data from Windows SharePoint Services You can now export a list in its Datasheet view from Windows SharePoint Services to a static table or to a linked table in Access. When you export to a static table, you create a table in Access. You can then view and make changes to the table independent of the original list in Windows SharePoint Services. Similarly, you can change the list in Windows SharePoint Services, and that will not affect the table in Access. When you export to a linked table, you create a table in Access and establish a dynamic link between the table and the list such that changes to the table are reflected in the list, and changes to the list are reflected in the table as well. Make a local table from a linked table In Microsoft Office Access 2003, you can make a local copy of the structure or data and structure contained in a linked table. XML support With the enhanced XML support in Microsoft Office Access 2003, you can specify a transform file when you import data from or export data to XML. The transform is then applied automatically. When you import XML data, the transform is applied to the data as soon as the data is imported, before any new table is created or an existing one is appended to. When you export data to XML, the transform is applied following the export operation. Often times a database contains lookup values that are stored in another database. You can now include these related tables when exporting. You can also include any predefined filter or sort order for an object when exporting the object. Security enhancements Macro Security Microsoft Office Access 2003 allows you to protect against potentially unsafe Visual Basic for Applications (VBA) code by setting the macro security level. You can set the security level so that you are prompted every time that you open a database containing VBA code, or you can automatically block databases that are from unknown sources. Additionally, Access uses Microsoft Authenticode technology to enable you to digitally sign a macro project by using a digital certificate. The certificate used to create this signature confirms that the macro originated from the signer, and the signature confirms that it has not been altered. When you set the macro security level, you can run macros based on whether they are digitally signed by a developer on your list of trusted sources. Block Potentially Unsafe Functions Access utilizes the Microsoft Jet Expression Service enhanced sandbox mode to block potentially unsafe functions from being used in expressions. |
#13
|
|||
|
|||
Moving OT: O2K2, O2K3 and O12
Pat Hartman(MVP) wrote:
I don't see much difference between the two versions. The next version of Access/Office will be DRAMATICALLY different. You may love it or you may hate it but everything you think you know about the Office interface you will need to relearn. So, my feeling is rather than fight to spend the money for O2003 licenses now, use the O2002 licenses and fight for the upgrade in next year's budget. Once you get past the interface changes, there are some awesome new features coming up in Access. I hate to say this before I've finished downloading the PDC 05 material made available by MS (thanks!), but I plan on viewing all of them if possible. In spite of the great feelings generated by Samba under Linux, managers and users here are leaning toward Microsoft. I feel that ignoring either MS or open source would be a serious mistake. So I'm looking at recommending a bunch of new 64 bit machines running MS OS with the first version of Access that works after Access 12 (SP 2?) along with some Linux boxes running OpenOffice in about a year from now. I think that the sooner the conversion is made to 64 bit the better given past experience. How well the new workflow paradigm will fit in with future plans is also a consideration. Microsoft is in a good position given the massive effort they've made to try to stay relevant (provided MS doesn't mess up Samba compatibility with their new servers). Six months ago the venture capitalists that were formerly employed by MS were putting more money into open source. I don't know if that's still the case. I'll know more about where I should be headed after I've viewed all the PDC 05 presentations. James A. Fortune |
#14
|
|||
|
|||
Access 2002 vs. 2003
Note that most of your users only need the runtime version of Access.
Your power users who create queries will want a full version of Access. I don't even think I have any users who create queries. Most users just use the app, perhaps doing some sorting or filtering, but that's about it. I used the Access 97 runtime, but haven't used it since. I remember that being problematic. Has it gotten better? Also, they run Office anyway, since they use Word and Excel. If we ran the Access 2003 runtime, that would be on top of Office Pro 2002. Sounds like that might be problematic. Furthermore you can easily use the new features of Access but create A2002 MDEs (using A2002) to distribute to your users. Yes, that's true, and that's a great idea. Since I connect through PCAnywhere to an admin machine for my use, I was thinking that I could upload the A2003 MDB; open it in A2002 on the admin machine, and then recompile it in A2002 for distribution. I guess that's the same concept only with an MDB. One thing that concerns me, though: I've heard that there are potential corruption issues when the db is developed and compiled in 2003 and then opened in an earlier version (even with it being in 2000/2 format). I have another client who is running Access 2003 and he would modify some forms and reports in the MDB and then send it back to me (MDB was kept in 2000 format). I would open it in A2000 and frequently one of the forms or reports that he modified was corrupted (could not open the code module for that object). We stopped having him modify the MDB directly, but just send me modified versions of the objects he changed, and the problem went away. So I'm concerned about using A2003 but recompiling and distributing in A2002. I'd also strongly suggest your network guy stage his upgrades. This month Win 2003 Server. Next month or two SQL Server. Later for Office. Besides those upgrades really don't care about the server. Hmm, the more I think about this, if he really wants to do all those upgrades at the same time, he's an utter idiot. I think he was thinking that he would have to reinstall SQL Server after the Windows upgrade, so he might as well install the new version. And, re. upgrading Office, it was because he "had to touch each PC anyway" (his words). And, yes, he is an utter idiot. Neil |
#15
|
|||
|
|||
Access 2002 vs. 2003
The only differences I saw were the
background shading and the rounded corners on buttons. Is there something else. no...nothing else. However, the rounded colors..and the xp theme do look quite a bit better. In that grid list..you can see one screen in the old format..and the rest are new...quite a nice improvement... Access 2003 uses a new file format (with the ability to still use the Access 2000/2002 format Actually, all 3 versions default to a2000 format. And, a2002 and a2003 share the same format... This was done to allow all 3 versions to work with each other.... So, the default format is a2000..and in for 02 and 03..they share the same format... -- Albert D. Kallal (Access MVP) Edmonton, Alberta Canada http://www.members.shaw.ca/AlbertKallal |
#16
|
|||
|
|||
Access 2002 vs. 2003
"Albert D.Kallal" wrote in message ... The only differences I saw were the background shading and the rounded corners on buttons. Is there something else. no...nothing else. However, the rounded colors..and the xp theme do look quite a bit better. In that grid list..you can see one screen in the old format..and the rest are new...quite a nice improvement... Yes, indeed! N |
#17
|
|||
|
|||
Access 2002 vs. 2003
Access 2003 uses a new file format (with
the ability to still use the Access 2000/2002 format Actually, all 3 versions default to a2000 format. And, a2002 and a2003 share the same format... This was done to allow all 3 versions to work with each other.... So, the default format is a2000..and in for 02 and 03..they share the same format... I'm a bit confused. Somewhere else I read someone give advice that if a db was developed in A2003 using A2003 format, that it couldn't be used in A2002; but if it was developed in A2003 using A2000 format, then it could be used with A2002, since A2000 and A2002 share the same format. If A2002 and A2003 use the same format, then why couldn't an A2003 database in A2003 format be used with A2002? Thanks. |
#18
|
|||
|
|||
Access 2002 vs. 2003
Also, I noticed that Access 2003 has SP2. I wonder if fixes in the new 2003
SPs would be propagated down to 2002 SPs. Probably not, would be my guess (but, then again, perhaps they don't need to be). N I am not sure what the fixes are, but they were major fixes. I believe if you go to Microsoft Office's site and then to Access, you should be able to search for what the fixes have been. The network guy is right, These fixes from 2002 to 2003 will be as service packs for 2002, but to save time, 2003 would be quicker. It is all a matter of time vs possible price. I am not sure if there is a difference in price but if there is, you would pay through time, if not in price. -- Joe Obergfell Web Developer |
#19
|
|||
|
|||
Access 2002 vs. 2003
"Neil" wrote:
Note that most of your users only need the runtime version of Access. Your power users who create queries will want a full version of Access. I don't even think I have any users who create queries. Most users just use the app, perhaps doing some sorting or filtering, but that's about it. I used the Access 97 runtime, but haven't used it since. I remember that being problematic. Has it gotten better? Troublesome, yes. But in an environment where you control the OS and software installs then they aren't usually a problem. Also, they run Office anyway, since they use Word and Excel. If we ran the Access 2003 runtime, that would be on top of Office Pro 2002. Sounds like that might be problematic. Slightly yes. But then uninstall the Access 2002 component of Office Pro. IOW there was no need to spend the extra $ on the Pro portion of Office Pro other than for those doing work on the MDBs such as you. Furthermore you can easily use the new features of Access but create A2002 MDEs (using A2002) to distribute to your users. Yes, that's true, and that's a great idea. Since I connect through PCAnywhere to an admin machine for my use, I was thinking that I could upload the A2003 MDB; open it in A2002 on the admin machine, and then recompile it in A2002 for distribution. I guess that's the same concept only with an MDB. Ayup. One thing that concerns me, though: I've heard that there are potential corruption issues when the db is developed and compiled in 2003 and then opened in an earlier version (even with it being in 2000/2 format). I have another client who is running Access 2003 and he would modify some forms and reports in the MDB and then send it back to me (MDB was kept in 2000 format). I would open it in A2000 and frequently one of the forms or reports that he modified was corrupted (could not open the code module for that object). We stopped having him modify the MDB directly, but just send me modified versions of the objects he changed, and the problem went away. So I'm concerned about using A2003 but recompiling and distributing in A2002. That's possible. I've been working in a similar environment recently without any such issues. But if you only use A2002 to create the MDE then that will reduce such issues. I'd also strongly suggest your network guy stage his upgrades. This month Win 2003 Server. Next month or two SQL Server. Later for Office. Besides those upgrades really don't care about the server. Hmm, the more I think about this, if he really wants to do all those upgrades at the same time, he's an utter idiot. I think he was thinking that he would have to reinstall SQL Server after the Windows upgrade, so he might as well install the new version. FWIW SQL Server 2000 and 2005 can coexist quite nicely. See "named instance" in the SQL BOL for more info. Essentially each named instance it's own install of SQL Server right down to the DLLs. Very nice for testing SP and patches, among other things. So let him install SQL Server 2005 now on his current server. Big deal. No, you really, really don't want to do too many upgrades at the same time. And, re. upgrading Office, it was because he "had to touch each PC anyway" (his words). Why does he even need to touch each PC for a server upgrade? Touch each users profile sure to setup the new server shares. Mind you I'm not at all familiar with what is required in a corp environment. Maybe that is indeed required. And, yes, he is an utter idiot. My sympathies. Tony -- Tony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm |
#20
|
|||
|
|||
Access 2002 vs. 2003
I'm a bit confused. Somewhere else I read someone give advice that if a db
was developed in A2003 using A2003 format, that it couldn't be used in A2002; You must have miss-read that. but if it was developed in A2003 using A2000 format, then it could be used with A2002, since A2000 and A2002 share the same format. If A2002 and A2003 use the same format, then why couldn't an A2003 database in A2003 format be used with A2002? You can use a 03 with a 02....they are the same format. since A2000 and A2002 share the same format No, they are different formats for 00 and 02. It is actually 02 and 03 that share the same format. (but, all 3 default to using the a2000 format). -- Albert D. Kallal (Access MVP) Edmonton, Alberta Canada http://www.members.shaw.ca/AlbertKallal |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Opening an Access 2003 database using Access 2002. | Chantel | General Discussion | 2 | September 1st, 2005 07:15 PM |
Book recommendations, please | Top Spin | New Users | 2 | March 1st, 2005 12:43 AM |
reports created with access 2002 do not work in access 2003? | Jerry Z | Setting Up & Running Reports | 1 | September 24th, 2004 07:27 AM |
Access 2000 DB in Access 2002 | Tony_VBACoder | General Discussion | 2 | July 28th, 2004 01:23 AM |
Access 2002 - 2003 and XP | Joseph Meehan | General Discussion | 1 | June 12th, 2004 07:00 PM |