Get to know your enemy: do you have older records in the company that show what passwords your developer used at that time, and in this case give you a hint on what he might have used for your db?
Could be faster than any other (more serious) method. My 2c. Roberto Grippi 2011/6/10 James Rankin <[email protected]> > Tried that, do File | Get External Data | Import, select the old 97 db, and > it bombs with "operation invalid without a current index". It then offers me > an Import Objects dialog, which is completely empty. Sounds like not only is > this ancient, it may well be damaged or erroneous too. When I try to "Repair > Database" from 97, it tells me there is an index problem. My day just keeps > getting better :-( > > > On 10 June 2011 13:07, Tony Patton <[email protected]> wrote: > >> Bit of a long shot, but have you tried importing everything into a new >> database in Access 2000? >> >> It's been a long time since I came across this. >> >> T >> >> Typed slowly on HTC Desire >> On 10 Jun 2011 13:02, "James Rankin" <[email protected]> wrote: >> > I have, I've cleared the password for the user Admin which is the db >> owner, >> > yet still, when I go to convert, I get the permissions error. I hope >> this >> > developer hasn't done something crafty to block the conversion. >> > >> > On 10 June 2011 12:59, Jonathan Link <[email protected]> wrote: >> > >> >> But perhaps, under 97 you can go in and turn off all the passwords... >> >> >> >> >> >> On Fri, Jun 10, 2011 at 7:56 AM, James Rankin <[email protected] >> >wrote: >> >> >> >>> Yes, I can open it in Access 97, but I am damned if I am sequencing up >> an >> >>> Office 97 app to run on our Windows 2008 R2 systems. >> >>> >> >>> I need to convert it to, at the very least, Access 2000 for it to be >> in >> >>> any way supportable, and even then it would only have to be for a >> short >> >>> period. Longer term we need to look to get this data put somewhere >> >>> completely different, but that's a whole different battle. >> >>> >> >>> >> >>> On 10 June 2011 12:46, Manuel Santos <[email protected]> wrote: >> >>> >> >>>> Can’t you find a machine with Access 97 installed? >> >>>> >> >>>> >> >>>> >> >>>> *From:* James Rankin [mailto:[email protected]] >> >>>> *Sent:* sexta-feira, 10 de Junho de 2011 12:16 >> >>>> *To:* NT System Admin Issues >> >>>> *Subject:* Re: Access form password >> >>>> >> >>>> >> >>>> >> >>>> Note the use of the word "drafting" >> >>>> >> >>>> When I cool off a bit I'll probably tone it down nicely :-) >> >>>> >> >>>> I still can't get this blasted thing converted. I tried running >> Access >> >>>> 2000 using the command line with the /convert switch and specifying >> the >> >>>> "Admin" username, but it just pops up a "Logon" box and rejects my >> >>>> credentials every time >> >>>> >> >>>> On 10 June 2011 12:05, Andrew S. Baker <[email protected]> wrote: >> >>>> >> >>>> Be thankful he was stuck using an older version of Access. >> >>>> >> >>>> Anyway, you're not out of the woods yet... >> >>>> >> >>>> Oh, and a snotty email isn't really going to help your cause here. >> Rather, send out a memo that indicates that you would like a meeting to >> discuss and uncover any other apps that are being used so you can ensure >> that they are backed up and supportable. You won't have to make any direct >> references to this incident, which helps people save face and makes them far >> more likely to cooperate with you. >> >>>> >> >>>> >> >>>> >> >>>> *ASB *(Professional Bio <http://about.me/Andrew.S.Baker/bio>) >> >>>> *Harnessing the Advantages of Technology for the SMB market...* >> >> >>>> >> >>>> >> >>>> >> >>>> On Fri, Jun 10, 2011 at 6:17 AM, James Rankin <[email protected] >> > >> >>>> wrote: >> >>>> >> >>>> Well I never - we have managed to dig the password out of it. The >> >>>> developer clearly wasn't as clever as he thought.... >> >>>> >> >>>> Now onto the next issue - whenever I try and open this database in a >> >>>> later version of Access, it tells me this >> >>>> >> >>>> [image: 3.jpg] >> >>>> Anyone have any ideas how to get around this bit? >> >>>> >> >>>> Cheers, >> >>>> >> >>>> >> >>>> >> >>>> On 10 June 2011 11:03, James Rankin <[email protected]> wrote: >> >>>> >> >>>> Thanks for the suggestion. Unfortunately that tool just, like many >> >>>> others, tells me the database isn't password protected. It isn't, per >> se. >> >>>> You can open the database, where you are met with this >> >>>> >> >>>> [image: menu.jpg] >> >>>> >> >>>> When you fail to get the right password for admin, this appears >> >>>> >> >>>> [image: password.jpg] >> >>>> >> >>>> Needless to say, I can't get into Design view - the database just >> closes >> >>>> automatically. >> >>>> >> >>>> This is very annoying, and I'm hoping the powers-that-be start taking >> >>>> notice of their serious lack of process and procedure which allows >> things >> >>>> like this to swim up and bite me on the ass. >> >>>> >> >>>> Grrr >> >>>> >> >>>> On 10 June 2011 10:48, Manuel Santos <[email protected]> wrote: >> >>>> >> >>>> As far as I remember, I once had a problem like that, and wasn't able >> to >> >>>> access some data on Access 97 database, and I used a tool to crack >> the >> >>>> password: http://www.rixler.com/eng/access_password_recovery.htm >> >>>> >> >>>> >> >>>> >> >>>> 2011/6/10 James Rankin <[email protected]> >> >>>> >> >>>> Another day, another episode of "I can't believe this has been >> allowed to >> >>>> happen" - yet here I am. >> >>>> >> >>>> We have a department that (unknown to me until today) are reliant on >> a >> >>>> database that was built (and still runs in!) Access 97. Yes, you >> heard me >> >>>> right. I mean, it only went out of extended support in February 2002, >> what's >> >>>> nearly ten years of unsupported software between friends? >> >>>> >> >>>> However (the plot thickens) it was built and maintained by a >> developer >> >>>> who has now left the company. And it needs some administration doing >> to it. >> >>>> And it turns out that the form to administer the database is >> >>>> password-protected. And not surprisingly, as with all problems that >> seem to >> >>>> have defeated everyone else, it is now sitting in my lap. The >> developer >> >>>> can't be contacted - believe me, short of commissioning a private >> >>>> investigator, I have tried all I can. >> >>>> >> >>>> The question is - does anyone know any way I could reveal or reset >> the >> >>>> password that is protecting the admin form? It's that long since I >> used any >> >>>> form of Access (never mind a 14-year old version of it!) that I am >> >>>> completely clueless here. >> >>>> >> >>>> I'm already drafting up a snotty email to go to the business heads >> here >> >>>> about the importance of migrating their critical data onto supported >> >>>> platforms, so hopefully something like this should never happen again >> (yes, >> >>>> it probably will, though). But if anyone can think of any way I can >> get >> >>>> inside the guts of this ancient database, I sure would be grateful. >> >>>> >> >>> >> >> >> > -- ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
