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 |
#21
|
|||
|
|||
"H" wrote in :
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). That would be lunacy of the highest sort for them to do so. It would mean the dropping of the MDB format, since IT'S A FRIGGING JET DB. Furthermore, Jet is not dead at all -- it's running ActiveDirectory's data store, for instance (this is why from Win2K on the Jet 4 DLLs are protected OS files). Jet will never be dropped unless Access completely drops all legacy support. It may be dropped as the default DB engine, but that would be stupid as well, since it would mean double workset (i.e., to open an MDB you have to have Jet loaded). -- David W. Fenton http://www.bway.net/~dfenton dfenton at bway dot net http://www.bway.net/~dfassoc |
#22
|
|||
|
|||
Tony Toews wrote in
: "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. Can't without dropping the MDB format entirely. Would you use Access if you had to use ADPs exclusively? Make MSDE the default database engine? That's fine by me so long as it's about as easy to use as Jet. There are terrible problems with conflicts between multiple applications installing the MSDE, since a lot of commercial applications use MSDE as their data store. I've run into with conflicts between Veritas Backup and Blackberry Server. It's a new form of DLL hell, and something that I really don't think any of us need. -- David W. Fenton http://www.bway.net/~dfenton dfenton at bway dot net http://www.bway.net/~dfassoc |
#23
|
|||
|
|||
On Tue, 18 Jan 2005 18:59:35 GMT, "Neil Ginsberg"
wrote: Actually, you've already got this MIS-feature in Access 2000. It is the so-called Name Autocorrect. The person who followed this post provided an excellent link to Allen Browne's paper on Name Autocorrect woes. Perhaps it would be easier if your work group established a set of naming conventions that everyone would adhere to. Well, it's not a workgroup. It's just me and the guy I'm working for, who likes to get his finger in the pie and rename things -- not just change the prefixes or whatever, but give them entirely new names. You need either Visual SourceSafe... or a baseball bat! John W. Vinson[MVP] |
#24
|
|||
|
|||
"David W. Fenton" wrote in message
28.78... "H" wrote in : 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). That would be lunacy of the highest sort for them to do so. It would mean the dropping of the MDB format, since IT'S A FRIGGING JET DB. Furthermore, Jet is not dead at all -- it's running ActiveDirectory's data store, for instance (this is why from Win2K on the Jet 4 DLLs are protected OS files). Jet will never be dropped unless Access completely drops all legacy support. It may be dropped as the default DB engine, but that would be stupid as well, since it would mean double workset (i.e., to open an MDB you have to have Jet loaded). -- David W. Fenton http://www.bway.net/~dfenton dfenton at bway dot net http://www.bway.net/~dfassoc Jet may not be dead but do you believe that any improvements will be made to security? Currently, anyone can break the security and I don't imagine MS are scurrying around in a desperate rush to fix this. |
#25
|
|||
|
|||
Well, over time he's mellowed out, as he's seen the amount of work I've had
to do to keep up with his changes. But he's just one of these compulsive "changers". "John Vinson" wrote in message ... On Tue, 18 Jan 2005 18:59:35 GMT, "Neil Ginsberg" wrote: Actually, you've already got this MIS-feature in Access 2000. It is the so-called Name Autocorrect. The person who followed this post provided an excellent link to Allen Browne's paper on Name Autocorrect woes. Perhaps it would be easier if your work group established a set of naming conventions that everyone would adhere to. Well, it's not a workgroup. It's just me and the guy I'm working for, who likes to get his finger in the pie and rename things -- not just change the prefixes or whatever, but give them entirely new names. You need either Visual SourceSafe... or a baseball bat! John W. Vinson[MVP] |
#26
|
|||
|
|||
Thanks for the input.
"Arvin Meyer" wrote in message .. . "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 |
#27
|
|||
|
|||
Per Neil Ginsberg:
Well, over time he's mellowed out, as he's seen the amount of work I've had to do to keep up with his changes. But he's just one of these compulsive "changers". Are you getting paid by the hour? If so, maybe just chalk it up to Job Security... -- PeteCresswell |
#28
|
|||
|
|||
"Steven Benn" wrote in message
... "David W. Fenton" wrote in message 28.78... "H" wrote in : 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). That would be lunacy of the highest sort for them to do so. It would mean the dropping of the MDB format, since IT'S A FRIGGING JET DB. Furthermore, Jet is not dead at all -- it's running ActiveDirectory's data store, for instance (this is why from Win2K on the Jet 4 DLLs are protected OS files). Jet will never be dropped unless Access completely drops all legacy support. It may be dropped as the default DB engine, but that would be stupid as well, since it would mean double workset (i.e., to open an MDB you have to have Jet loaded). Jet may not be dead but do you believe that any improvements will be made to security? Currently, anyone can break the security and I don't imagine MS are scurrying around in a desperate rush to fix this. As far as I can tell, no file-based application can be made totally secure. -- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (no e-mails, please!) |
#29
|
|||
|
|||
Yeah, I get paid for it. But it's damn frustrating. You want to see a final
product eventually. But between continually renaming objects or redoing how forms work, it's a perpetual development cycle. "(Pete Cresswell)" wrote in message ... Per Neil Ginsberg: Well, over time he's mellowed out, as he's seen the amount of work I've had to do to keep up with his changes. But he's just one of these compulsive "changers". Are you getting paid by the hour? If so, maybe just chalk it up to Job Security... -- PeteCresswell |
#30
|
|||
|
|||
lol....when management has "control over" the developer, a database is never
finished - until it's dropped altogether for something else... g "Neil Ginsberg" wrote in message link.net... Yeah, I get paid for it. But it's damn frustrating. You want to see a final product eventually. But between continually renaming objects or redoing how forms work, it's a perpetual development cycle. "(Pete Cresswell)" wrote in message ... Per Neil Ginsberg: Well, over time he's mellowed out, as he's seen the amount of work I've had to do to keep up with his changes. But he's just one of these compulsive "changers". Are you getting paid by the hour? If so, maybe just chalk it up to Job Security... -- PeteCresswell |
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 10:15 AM |
Is MS Access XP Version compatible to Visual Basic 6 ? | rock72 | General Discussion | 2 | December 6th, 2004 06:42 PM |
is Access 2003 any better than XP? | Gorb | General Discussion | 4 | November 11th, 2004 09:44 PM |
is Access 2003 any better than XP? | Gorb | Using Forms | 2 | November 11th, 2004 09:20 AM |
Access XP Compared to Access 2003 | Mardene Leahu | New Users | 1 | October 1st, 2004 05:11 AM |