[AccessD] DeCorrupter Info

[Fred Hooper]

I’ve been thinking of doing so and will.

While I’m waiting for it to arrive I’ve found some interesting things in a
search — just on my phone but one thing that stuck through the tiny screen
was that the issue can be caused by converted databases and isn’t caused by
imported. I’ll try importing everything into a clean db and see if that
helps.

Thanks, Fred

On Fri, Feb 16, 2018 at 5:28 PM Dan Waters <df.waters at outlook.com> wrote:

> Hi Fred,
>
> I wrote the DeCorrupter using Access 2010 on W10 and all still works well.
>
> Do you have an option to use Access 2003?
>
> Dan
>
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> Fred Hooper
> Sent: February 16, 2018 15:13
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] DeCorrupter Info
>
> I've hit a wall, probably caused by Windows 10.
>
> I installed Access 2002, including all KB's and SP3 on a new machine.
> After I found the KB's that MS had removed from their web site I had no
> further issues. I set MSACCESS.EXE to compatibility mode for SP3 as I had
> on my previous machine.
>
> Working with the DeCorrupter is my first use of Access on this machine.
>
> The DeCorrupter can't create either forms or reports from the text files;
> it has no problems with queries or modules.
>
> I suspected that it was a security issue, so just after the destination
> file was created I paused the processing and allowed Everyone full control
> of the destination file. I checked again before the program renamed and
> cleaned up, Everyone still had full control. In between, each form and
> report failed with Error 2285: Microsoft Access can't create the output
> file for the respective LoadFromText commands.
>
> As this same code worked fine on my departed Win 7 machine, I'm not sure
> what to do. Does anyone have any ideas?
>
> TIA,
> Fred
> > Dan Waters <mailto:df.waters at outlook.com> Friday, February 16, 2018
> > 12:43 PM Hi Fred,
> >
> > I had no idea that you had looked at this so thoroughly and made
> > valuable changes. This DeCorrupter was written in Access 2010 -
> > although I created the file as an .mdb.
> >
> > I don't have all the different versions of Access - I'll probably need
> > to find a way to run test with all the versions.
> >
> > I sent Carolyn a test version to get more filepath information - We'll
> > see what happens.
> >
> > And - you mentioned that I could find the changes by looking for FAH
> > in the modules - but where can I find those modules?
> >
> > Thank you!
> > Dan
> >
> > -----Original Message-----
> > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf
> > Of Fred Hooper
> > Sent: February 16, 2018 11:30
> > To: Access Developers discussion and problem solving
> > Subject: Re: [AccessD] Dirty Cancel Clear all controls
> >
> > Hi Dan,
> >
> > The decorrupter has an implicit assumption that the MDB being
> > decorrupted is being run (in the decorrupter) by the same version as
> > created it; it obtains the Version from Application.Version -- which
> > refers to the EXE, not the MDB. In thinking about it, I believe that's
> > the only way you could create the decorrupter program; perhaps if the
> > versions are close it works properly, but the 10 years between
> > Carolyn's versions probably brought too many changes.
> >
> > So decorrupter is identifying Carolyn's code as version 14 and
> > attempting to export/import a version 9 mdb.
> >
> > Carolyn, I think you have two choices:
> >
> > * Convert your program to some other version and use that version to
> > run the decorrupter.
> > o 2002 (10) and 2003 (11) are most similar, but the original
> > decorrupter didn't handle them. My modifications to do so are
> > incomplete, although I'm taking another pass at them today.
> > o Versions 12-15 are fully supported by the decorrupter.
> > + If I were you (and 2010 permits) I'd convert the MDB to 2010
> > (14) and then run the decorrupter. If the program runs properly
> > afterwards you're set -- and can run it again if you need to.
> > + If that doesn't work and you can't find an older Access
> > version closer to home I'll convert it to 2002, run the decorrupter,
> > and send it back to you.
> > * Don't use the decorrupter.
> >
> > Dan, in this second look for me, I noticed that I added new Version
> > logic code only in TransferOptions. I probably should add it in
> > TransferProperties too. This might be the explanation for the 4
> > failures to export that I discuss in my Other Access Versions module.
> > I dealt with them by just importing them into the decorrupted MDB; the
> > 200+ successes solved my problems. (You can find my changes by
> > searching for FAH in the modules.)
> >
> > Best,
> > Fred
> >
>
> --
> 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
>