Dameon

Okay, last effort... installed a fresh copy of Windows 7. Installed Access Runtime 2010. Rebooted. Installed Access Runtime SP1. Rebooted. Installed GaMaDaBa. Rebooted.

It worked. The application actually launches and seems to work! I was beginning to wonder if this application was a cruel trick to all the end users, but on April 1st (of all days), I was able to get it functioning.

Now. Figuring out the program is another daunting task. But I won't bore you with those escapades.

Thanks Keyser!

The thing is, the .NET framework doesn't automatically get the environment path which is %ADO% due to that, the path won't matter... the error is caused by the code not expanding the environment variable before using it...

I am certainly inclined to agree with you as that %ADO% looks more like what you're saying as opposed to a $ADO which would be more likely a variable issue. But obviously the code is expanding it right on "some" installations, so the code is working in "some" cases. Maybe I'll run a .NET update.

I'm beginning to think it might be easier to bring my 360 to a friends house with Internet and just update my covers that way. I really didn't think this would be that big of a deal. Geez.

I checked my environment variables, and noticed %ADO% wasn't set, so I set it to the path above. Same error.

Okay, had a few minutes to mess with this again, but still not making progress.

Configured a fresh, new, unaltered, VM with Windows XP SP3. Downloaded Access 2010 Runtime and Access 2010 Runtime SP1. Downloaded GaDaBaMa 3.2. Took a snapshot. Installed Access 2010 Runtime and Access 2010 Runtime SP1. Took a second snapshot. Installed GaDaBaMa 3.2. Everything (Access, SP1, GaDaBaMa) installed without error.

Ran GaDaBaMa:

Verified the file exists in C:\Program Files\Common Files\System\ado (it does, along with 6 other versions).

What next? This seems like a lot of work for something that does seem to work for some people. How much more vanilla can you get than a fresh install of the OS and nothing else installed except the application?

Thanks.

You need Access Runtime 2013 for the Access 2013 version. If another Access version is detected the installation can't proceed.

So your suggestion of trying the 2013 version won't work? Can I have the full 2010 version installed along with the 2013 runtime version? Otherwise I guess I have to fire up another VM just to run this application.

Seems like it'd be easier for the Freestyle database to be manually manipulated to force path names and image locations. Maybe that's the ticket. I'll just go through the various .db files in the Freestyle directory and see which ones open in Access. If I could see one example table, I could figure the rest out. If they are keeping the images in the database, that's a little more complicated, but still quite doable. Being an old hand at MySQL, maybe I'll try that as well. If you're using Access to manipulate the database, then that's probably what I should stick to.

I've never tested Access 2010 SP2, Back then, Err2425 happened when SP1 was not installed. Maybe SP2 is not compatible and would need a new package.

Either use SP1 or try the 2013 version.

Didn't work with SP1, so I installed SP2 in an attempt to fix it. Same thing you see above in SP1 and SP2.

Your installer won't allow me to install the Access 2013 version:

Maybe the installer should prompt "Do you want to continue anyway?" instead of pigeon holing me into clicking Cancel.

Thanks for your response.

Ok, I've read all 8 pages of this thread (including the links to xboxpirate.eu) and performed various searches on this forum, but still have no resolution.

I am running GaDaBaMa 3.2:

I am running Access 2010 SP2:

I downloaded GaDaBaMa 3.2 and ran the install without error or issue. When I run the application, I get the following sequence of windows:

I click OK:

I click Stop All Macros:

I get this popup three times. I click OK each time:

I click OK:

The popups go between the previous two windows five times. Then I get this:

I get this popup four times. I've tried clicking OK and Cancel. Both result in the application closing back to the desktop. Nothing further happens. I also tried running as Administrator with no change in behaviour.

Any suggestions?