Minor Problems

[ddouglass]

Bryan.
I have a couple of questions relating to the database files used by Hoster.

1. Are you aware that when Hoster is installed on a system that also has Microsoft Access (Office 2003) installed, Hoster is interfering with Access?

This is occurring because both programs are using the same type of database files. After using Hoster, if you try to open an Access database file (mdb) by double clicking on the file Access gives you an error stating you need to re-install Office or Access. If you open Access first, then open the file from within the program it works, but doesn't correct the error. The only correction is to go to the file properties and reset the "Opens with:" program. Even if the correct program is listed you have to re-apply it.

2. Does MTU have any plans to update the version of Access db file you are using from the "97" to one of the more current versions? I have a feeling that if Microsoft follows their normal path the next version of Access after "2003" will not be able to read these files.

I don't know what percentage of your users have Microsoft Office or even Access installed with Hoster on a system together but thought you might like to know of a potential problem.

Thanks for all the close support and attention you guys are giving to this great program. It is comforting to know that someone cares about their users after the purchase has been made. This seems to be so rare these days.

[nreel]

Hoster JET Database is 97. When Hoster is installed, you computer gets temporarily dedicated to Access97.

NOT BY CLICKING and ACCESS DB FILE, but by simply Opening and Closing Access20xx will correct the OPEN WITH program status on your Computer, as you found out, so that, upon Clicking an Access MDB file, the MDB file will OPEN properly.

Of course, one problem with not using Access97 FULL is that you can't change any 97 DB OBJECTS unless the 97 DB is converted to a 20xx DB, first. And, once the 97 DB is converted to a 20xx DB you can't use it in Hoster…such as converting the Hoster Song.MDB to a 20xx DB.

But, Since DBs are MEMORY Hogs, it probably makes sense to use the earliest Access DB Version as possible, and, a DB Version that is STILL available on the Market, which Access97 is, and, I purchased a copy.

When I first purchased Hoster, MTU was using Access 1.0. My Access2000 would not convert an Access1.0 DB. So, I understand what you mean when you say that "X" versions Up-The-Line will NO LONGER OPEN "X" versions Down-The-Line, and, I was very Happy when MTU, finally, upgraded to Access97. At least, now, I could CONVERT the 97 DB to an Access2000 format.

But, it was a pain every time I wanted to manipulate the Songs.MDB with Access2000. Of course, if I had purchased Access97 at some point prior to MTU upgrading to Access97, I would have been able to OPEN the prior Access1.0 DB, which would have saved me some grief, but it still would have been a pain to have to Convert.

Consider that, if MTU upgraded their Access DB every time Microsoft came out with a new Access version, anyone having a DIFFERENT Version would have the SAME problem with his or her Access Versions not working properly each time Hoster was Installed.

So, it, probably, makes sense that Access97 is used.

I, for one, don't want to buy Access to keep matching what MTU decides to change to.

I'm just glad I was able to obtain Access97. It has made working with Hoster's Songs.MDB 1000% easier.

Norm

[ddouglass]

Norm, that would be ok and I would go out and purchase 97, except that I need my 2000 version database files to work and I have several. I haven't tried to manipulate either of the Hoster mdb files, but I still have the problem that they won't open from the file or shortcut. I can go in Access and correct it but Hoster resets this every time the computer starts or restarts.

The solution for me would be for Hoster not to set this function until the program starts up instead of on boot up. And should reset it back when Hoster is closed.

The question on upgrading was just a curiosity question, not pushing for an upgrade. Though it would be nice and a whole lot easier to correct and manipulate without having to convert twice. Or we could subscribe to the "If it ain't broke, don't fix it." theory and ignore progress.

[nreel]

Well, for me, that is it..."it ain't broke, so don't fix it."

I use a program that allows Singer's to search and submit their songs via Computer Terminals through a network. I do not use PRINTED Song Lists (aka SongBooks) or Song Slips anymore. This program grabs all the Artist and Title info straight from the SONGS.MDB, which is based on Access97. If Hoster changes, I could be dead in the water if the other software doesn't know what to do with a later version of Access.

Unlike Printed Books, where one may reprint them once a year, I can UPDATE my COMPLETE listing in my "CYBER Books," at any time, which may include changes to Current info. This means that I may have DAILY interaction with my DB, such as finding a Misspelled and/or Duplicate Entry, correcting it/them Immediately, and Transferring the Updated DB to the "Cyber" Computers for Immediate use.

If I were still using Printed Song Lists, an MTU "ACCESS" upgrade may not affect me for several months.

Norm

[UPNext]

Hi Nreel,

I was wondering what network program you were using to allow your singers to lookup and submit songs to your Hoster PC over a network. Are you using a wireless network and thin clients as the singers workstations? The idea sounds interesting and I'm just curious as to how it actually works.

Thanks,

Upnext

[songpony]

I'd also like info on how a singer would submit a request over the network (how do they send it, where does it go, etc.). I've had people ask me about this, but I have no clue how to implement it (or how many "terminals" it would require, etc.). Thanks.