[admin]

Originally Posted by FRadspinner

Instlled Hoster Lite 5.05. Made all the required changes and it was working. Then after installing Microstoft Office, Hoster would not open up anymore.

This is the situation I was working from. Hoster was installed along with the Access JetEngine. THEN... Office/Access was installed, which "I believe" would overwrite the JetEngine Hoster had previously installed.

Originally Posted by admin

When Hoster is installed, we also install the Access "JetEngine" for Access 97, which is what Hoster requires. This is the under-the-hood code that Access uses.

When you installed Office which included Access, it REPLACED our JetEngine with a newer one Hoster won't work with.

I'm surprised that removing Office w/Access didn't allow Hoster to run again after re-installing.

I added the as I don't know for sure. I discussed this with MTUSUPPORT this afternoon and he had not (except a long time ago) installed Access AFTER Hoster was installed. We will need to take a new system that doesn't have Access on it and try this sequence.

Originally Posted by FRadspinner

That's interesting, what you said about Microsoft Access replacing the Access Jet Engine you use for Hoster. I have an older version of Hoster, I think 4.11. I already had Access 2007 installed when I installed my Hoster Lite on my Laptop.

The sequence here is Access is installed, then you install Hoster's Access Jet engine... AFTER. This actually tends to confirm what I'm proposing as the cause. "I believe" this sequence works as that's what happens under 99.99X% of our Hoster users.

Originally Posted by FRadspinner

I run WindowsXP. I have no problems with the Access Database that Hoster uses to store the song information. As a matter of fact, I make a copy of it (being careful not to change anything in the original file) and create a new database in Access that I can revise to print off my Song Books.

I am 99.999% sure that if you open either the songs.mdb or singers.mdb into any Access higher than Access 97, when either is OPENED, it is converted to the format of that Access version. We have some singers.mdb's from user with problems, and they definitely had been damaged in a way that even Access - in theory - would never do; we could copy a record including the SingerID field, then pasted it as a new record at the bottom. The SingerID was copied without being incremented to an unused number. Then 2 copies of that SingerID existed, and everything went downhill from there on. Access should NOT allow this, but it did. The users could not say what they did that damaged "something" deep in the .mdb file.

Originally Posted by FRadspinner

Does what you speak of only happen in the Windows7 version of Hoster - Access replacing the Access Jet Engine for Hoster? Or does this happen only if you install Access after you already installed Hoster?

This is my general understanding of how WINDOWS installs LATER DATED program files REPLACING prior dated versions of the same named file. IF... Windows 7 changed this, I don't know.

I'll bring this up in our staff meeting tomorrow for discussion.