John Clark
John.Clark at niagaracounty.com
Mon Jul 15 09:54:38 CDT 2013
Wow! This was way more work than it should have been. There were so many issues that I ran into...EVERYTHING that I did had a little caveat or hurdle. I have 2 laptops and a PC on my desk, all doing their own part in this. I did most of the work on a laptop with Win 95 & Access 97 on it. This allowed me to avoid all the issues of A97 on newer PCs. The other laptop was suppose to do this, but it ended up being just a go between from the other laptop to my PC and the network. I got most of it done by Thursday afternoon...maybe it was Friday morning...it is all blending now. But, this "program" consisted of 3 MDBs...a Front-end, a Back-end and that BE database also linked to another DB w/only 2 tables in it. The front-end and that 2-tabled DB both came over relatively OK, but the BE was a pain. For some reason, only 18 of 19 tables would come over. I kept getting errors no matter what I tried...which consisted of many things. The main error, as I posted before, was that two people were trying to make changes at the same time. This was not the case though. It was suggested that it was corrupt and I needed to compact and repair. I did...several times...w/no improvement. This morning I got the idea to just recreate that table and try to import data only. There were only 9 fields, so I did this, but it wouldn't import the data...I think this was more of a restriction of the PCs power...maybe. But, instead of beating my head on the wall over this, I immediately tried to copy the data into Excel, and it worked. There was one single record that seems to be an error, and I omitted that, but the rest went fine...over 20k records. It wouldn't import into the table I created...I don't understand it but that also seems to contain the error record...it appeared on its own, so there is something to this. So, I instead imported into a new table and then tweaked it to match the original. I then imported that new MDB to the other location where all is how I want it, and it looks to work fine. NOW...I'm to the point where I need to update. I initially tried...for the heck of it...to jump right up to 2010, but that didn't go real well...not real bad either, but its pretty much an all or nothing deal, right? So, I'm loading 2003 to a PC and plan to upgrade to 2003. (A) I think my chances for success are better w/2003, and they have 2007 anyhow, which will run 2003 fine. And, I just read this morning, an article from MS that said, "to upgrade to 2007, you must first go to 2003 and then to 2007." I never heard that before, but if they say so... Is this really the case though? >>> "Jim Dettman" <jimdettman at verizon.net> 7/12/2013 11:32 AM >>> "It says, "the microsoft jet database engine stopped the process because you and another user are attempting to change the same data at the same time." This is NOT the case though. " DB is most likely corrupt: ACC: Jet Database Engine 3.x Error Messages Due to Corruption http://support.microsoft.com/kb/182867 Make a backup copy and run a compact and repair on it. Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Clark Sent: Friday, July 12, 2013 10:30 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Getting around old workgroup security Well, I've basically done all of this, and all was looking good, until... The main db (front-end) links to two other dbs. And, that 2nd db...housing most of the data...also links two tables to the 3rd db...both the front-end, and the one back-end link to the 3rd db, which has only 2 tables. I found the user-level security wizard and ran that for each of the 3. 2 were fine, but the db w/all the data errors out. It says, "the microsoft jet database engine stopped the process because you and another user are attempting to change the same data at the same time." This is NOT the case though. I have a feeling that, if I could get past this road block, that it would be my last. >>> "Heenan, Lambert" <Lambert.Heenan at aig.com> 7/12/2013 9:05 AM >>> Quote from the horse's mouth: " 34.How can I "de-secure" a database? You need to have Administer permissions and/or be a member of the Admins group. Grant full permissions to the Users group and the Admin user account. Put the Admin user back in the Admins group and remove the password from the Admin user. You will not be prompted for a logon ID and password once the password is removed from the Admin user. Optionally, you can also run the Security Wizard again to transfer ownership of all objects back to the Admin user, but the wizard will also remove permissions from the Users group, which you may not want. " Lambert Notice: This electronic transmission is intended for the sole use of the individual or entity to which it is addressed and may contain confidential, privileged or otherwise legally protected information. If you are not the intended recipient, or if you believe you are not the intended recipient, you are hereby notified that any use, disclosure, copying, distribution, or the taking of any action in reliance on the contents of this information, is strictly prohibited. Niagara County is not responsible for the content of any external hyperlink referenced in this email or any email. IF YOU HAVE RECEIVED THIS TRANSMISSION IN ERROR, PLEASE NOTIFY THE SENDER IMMEDIATELY BY EMAIL AND DELETE THE ORIGINAL MESSAGE ALONG WITH ANY PAPER OR ELECTRONIC COPIES. Thank you for your cooperation. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com Notice: This electronic transmission is intended for the sole use of the individual or entity to which it is addressed and may contain confidential, privileged or otherwise legally protected information. If you are not the intended recipient, or if you believe you are not the intended recipient, you are hereby notified that any use, disclosure, copying, distribution, or the taking of any action in reliance on the contents of this information, is strictly prohibited. Niagara County is not responsible for the content of any external hyperlink referenced in this email or any email. IF YOU HAVE RECEIVED THIS TRANSMISSION IN ERROR, PLEASE NOTIFY THE SENDER IMMEDIATELY BY EMAIL AND DELETE THE ORIGINAL MESSAGE ALONG WITH ANY PAPER OR ELECTRONIC COPIES. Thank you for your cooperation.