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
|
|||
|
|||
H,
Please do NOT attach binaries to posts in non-binary newsgroups, particularly 500+kb bmp files that could have been done as a 30kb jpg. Thanks, Bri H wrote: Just some thoughts |
#12
|
|||
|
|||
"Neil Ginsberg" wrote in message ink.net... "Mike Turco" wrote in message news:lw3Hd.8274$nt.1238@fed1read06... "Neil Ginsberg" wrote in message news I wrote we're using Access 2000, not 2002. I agree re. 2002/2003. Neil, I haven't seen anything new and great since A97. (A2 was 16 bit and A95 was a piece of junk.) I keep upgrading because all my customers upgrade. I agree re. A97. I think A97 was a real breakthrough in reliability. I'm not particularly impressed with ADO, the ASP pages or any of this newer stuff. Unless you have a specific reason to upgrade I would suggest that you stay with what you have. One concern is that A2000 is now 5 years old, and MS won't support things indefinitely. That's a really good point. I really like the backward compatibility of Access, although its not quite perfect. I have another client who ... [is] notorious for renaming objects as he thinks of a better name. Drives me crazy! Name game? Well, the re-name game :-) Mike |
#13
|
|||
|
|||
It's safe to say that Microsoft want to drop support for jet and make MSDE
the default database engine (we know it can be installed silently and without user input). Yes, that's their intention. But I can't imagine them dropping support for Jet, with the huge number of Jet databases in use. Neil |
#14
|
|||
|
|||
One concern is that A2000 is now 5 years old, and MS won't support things
indefinitely. That's a really good point. I really like the backward compatibility of Access, although its not quite perfect. And added to that is that the upgrade to A2003 should be pretty straightforward. The next version of Access, though, will most likely use VBA.NET and would require significant changes to upgrade. Thus, upgrading now, while A2003 is the current version (and available) may be the best move. OTOH, seems that nothing new is coming out for a while anyway, so.... Neil |
#15
|
|||
|
|||
If you do a lot of VBA coding, there are some improvements that I now find
it hard to do without when working in A97. Custom events, Custom events? Haven't seen that in A2000. What are they? custom enumerated types, and CallByName, CallByName? Another new one. to name a few. Also, having the VBE in a separate window, though initially annoying, shows its value the first time you debug code behind a modal form. Yeah, I know. For me, it's just the ability to use Alt+Tab (which I can do without looking) to go to the code window, as opposed to Ctrl+F6 (which requires much more work). Also, being able to have a certain form be the current one, and a certain code module, and flip back and forth, instead of having to scroll through all forms and code modules that are open (arggggh! just the thought! :-) ). Neil |
#16
|
|||
|
|||
"Neil Ginsberg" wrote in message
nk.net... Does anyone know if a new version of Access is due to come out anytime soon? I think you'll find that both Access 2002 and 2003 are significantly more reliable, especially during development, than Access 2000. Access 2003 has slightly better help files than 2002, both of which are better than 2000, BUT not as good as Access 97. Access 2003 does not have an index on it's help files, and by default wants to connect you to the Internet to get help. A 2003 has solved the Name AutoCorrect bug and fixed some of the other corruption bugs that plague A2000. I think either A2002 or A2003 is a worthwhile upgrade. Access 12 (the next version) will have some nice features, but won't be out for some time, so you may not want to wait. -- Arvin Meyer, MCP, MVP Microsoft Access Free Access Downloads http://www.datastrat.com http://www.mvps.org/access |
#17
|
|||
|
|||
"H" wrote:
t's safe to say that Microsoft want to drop support for jet and make MSDE the default database engine (we know it can be installed silently and without user input). X Want to drop support for jet? Possibly. But they never will. It's in way too many systems now. Make MSDE the default database engine? That's fine by me so long as it's about as easy to use as Jet. 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 |
#18
|
|||
|
|||
Trevor Best wrote:
The dreaded Name Autocorrect feature, would be nice if it weren't so bug ridden. I've been using it the last few weeks in A2003 and it's been quite smooth for me. So far anyhow. Quite nice too. 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 |
#19
|
|||
|
|||
"Arvin Meyer" wrote:
I think you'll find that both Access 2002 and 2003 are significantly more reliable, especially during development, than Access 2000. Agreed. I found that doing work in A2000 a form would corrupt about once a week or so. A2003 hasn't had this problem at all. Also I really like the smart tags Access pops up on the controls. For example I added some &s to some unassociated labels. Access promptly tells me they're unassociated and gives me an option to associate the label to a control. Nice. Or if you've renamed fields in the tables the controls based on the old names are obviously incorrect. Now a little triangle appears in the corner. Again nice. Created my first report and I see a little flag in that little grey box in the upper left hand corner of the report. I click on it and see a "Common Report Error" "Report width is greater than page width" with a bunch of options. Very nice. I can see how this would help the newbie/itinerant Access users. I also see lots of flags for the label controls in the headers. Someone spent some time on these little touches. 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
|
|||
|
|||
"Mike Turco" wrote in
news:lw3Hd.8274$nt.1238@fed1read06: There have been some nice incremental improvements. For example, if you change the name of a query, and you have a report based on that query, the report will automatically updated to reflect the changed name. That's a nice feature -- renaming objects used to be so difficult. (There are some drawbacks too. The name game is best avoided.) That's one of the *worst* features of A2K and its successors, and it's (Name AutoCorrect) the first thing any experienced developer will turn off. -- David W. Fenton http://www.bway.net/~dfenton dfenton at bway dot net http://www.bway.net/~dfassoc |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Running Spanish Access application into English version | Joseph | New Users | 0 | December 15th, 2004 11:15 AM |
Is MS Access XP Version compatible to Visual Basic 6 ? | rock72 | General Discussion | 2 | December 6th, 2004 07:42 PM |
is Access 2003 any better than XP? | Gorb | General Discussion | 4 | November 11th, 2004 10:44 PM |
is Access 2003 any better than XP? | Gorb | Using Forms | 2 | November 11th, 2004 10:20 AM |
Access XP Compared to Access 2003 | Mardene Leahu | New Users | 1 | October 1st, 2004 05:11 AM |