StaRKeY
starkey at wanadoo.nl
Mon Jul 12 13:30:46 CDT 2004
Well Charlotte to be honest I'd recommend you should... I was using Office 2K on Win2K before upgrading to 2K3 and it went like a charme for me... Just like 1-2-3, updating no problems, even though the upgrade went from UK english to Dutch... First time for me a ms product installed so smoothly:-) And for those interested A2K3 is able to handle filesystems from 2K /2K2 and ofcourse 2K3 which is also a big plus not to mention the ability to use DotNet instead of VBA and a lot of other nice goodies... I think it's a good time to upgrade to 2K3 if you're still using A2K or A97, a lot of ADO stuff is actually working and improved like being updatable, more XML options... In short, I like it so far:-) Regards, Eric Starkenburg -----Oorspronkelijk bericht----- Van: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] Namens Charlotte Foust Verzonden: maandag 12 juli 2004 19:02 Aan: Access Developers discussion and problem solving Onderwerp: RE: Subject: RE: [AccessD] db1, 2, 3 ........ I don't think you mentioned A2003 in your original post. I haven't ventured into those water yet. Maybe I won't. ;-} Charlotte Foust -----Original Message----- From: Hale, Jim [mailto:Jim.Hale at fleetpride.com] Sent: Monday, July 12, 2004 8:41 AM To: 'Access Developers discussion and problem solving' Subject: RE: Subject: RE: [AccessD] db1, 2, 3 ........ Well its good to know I'm not crazy. (At least on this particular subject. I told the voices if they didn't shut up I'd poke 'em with a Q tip again. that seemed to quiet them) :-) Jim Hale -----Original Message----- From: Jim Lawrence (AccessD) [mailto:accessd at shaw.ca] Sent: Saturday, July 10, 2004 2:04 PM To: Access Developers discussion and problem solving Subject: RE: Subject: RE: [AccessD] db1, 2, 3 ........ Yes, I have. Some other issues, I have ran into are: 1. Having to exit and restart Access again, after running an application, before being able to do anymore coding. 2. Having to install A2003, as many as four time before the product stabliized. 3. Having to reboot before A2003 will recognize an update even though it was not requested. There are a few other but those are the high-lights, Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Hale, Jim Sent: Friday, July 09, 2004 9:16 AM To: 'Access Developers discussion and problem solving' Subject: RE: Subject: RE: [AccessD] db1, 2, 3 ........ Slightly different question- have you run into cases where after "x" number of changes to code Access just decides not to run them, ie it just executes the old code and completely ignores the new? It is extremely annoying. The only cure I've found is to import everything into a new database container. Jim Hale -----Original Message----- From: Charlotte Foust [mailto:cfoust at infostatsystems.com] Sent: Friday, July 09, 2004 10:16 AM To: Access Developers discussion and problem solving Subject: RE: Subject: RE: [AccessD] db1, 2, 3 ........ The db1.mdb, etc., files are compacted copies of the database that couldn't be renamed, perhaps because the original couldn't be deleted for some reason. If you're spawning those, then you probably aren't actually compacting your database even though you may think you are. If the database is in a partially compiled state (this is a VBA project issue, not compact and repair), then that might be what is causing the problem. Try turning off the autocompact and then using the decompile switch to open the database and use the bypass key to avoid running any code. Then close the database, reopen without the decompile switch but using the bypass, and compile and save the VBA project. Then try turning compact on exit back on and see if that cures the problem. Charlotte Foust -----Original Message----- From: pedro at plex.nl [mailto:pedro at plex.nl] Sent: Friday, July 09, 2004 1:21 AM To: AccessD at databaseadvisors.com Subject: Subject: RE: [AccessD] db1, 2, 3 ........ Hello Charlotte, i indeed have turned on Compile (compact and repair) after Exit, and indeed its a permissions protected database. So i can delete these db1.mdb etc without any troubles?? Another question: Is compiling after exit a good option, because the fact that in this way the database several times a day wil be compacted. Pedro Janssen From: "Charlotte Foust" <cfoust at infostatsystems.com> To: "Access Developers discussion and problem solving" Date: Thu, 8 Jul 2004 14:01:58 -0700 Subject: RE: [AccessD] db1, 2, 3 ........ Do you have Compile on Exit turned on? I've usually seen that kind of thing when the database attempted to compact but for some reason (often permissions), it couldn't delete the original and rename the db1.mdb, etc. Charlotte Foust -----Original Message----- From: Pedro Janssen [mailto:pedro at plex.nl] Sent: Thursday, July 08, 2004 12:56 PM To: AccessD at databaseadvisors.com Subject: [AccessD] db1, 2, 3 ........ Hello Group, i have an front & backend mdb on a server. The front-end creates temporary?? databases named as db1.mdb, db2.mdb, db3.mdb etc. each with different filesize. Why is this and why are these not deleted automatically? TIA Pedro Janssen -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _____ avast! Antivirus <http://www.avast.com> : Uitgaande bericht is niet besmet. Virus Gegevensbestand (VPS): 0429-0, 12-07-2004 Getest op: 12-7-2004 20:30:46 avast! auteursrecht (c) 2000-2004 ALWIL Software.