Problem getting Bala Boss working

We're trying to install a software called BalaBoss Client Navigator (v8.06) onto a Terminal Server (Windows 2003 R2) for a client.

We have mapped the application to the proper data file, using the installed "Workgroup Administrator" application it comes with.

When you open the application, you get past the login screen.  It start to load the file, but stops at 10%, and then the application closes.

When I check the event viewer, I get the following Application Error.

Category: 100
Type: Error
Event ID: 1000
Description: Faulting application MSACCESS.EXE, version 8.0.0.5903, faulting module unknown, version 0.0.0.0, fault address 0x0455b0f0.  For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Based on my knowledge of this application, I believe it to be based on MS Access.  They have had issues with it before, but that was solved by installing the Bala Boss software BEFORE installing the MS Office suite of applications.  We did install Bala Boss before office, but are still having this problem.  
sanderrobAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

puppydogbuddyCommented:
see this link...it is an FAQ/troubleshooter for BalaBoss installations. You need to go over the checklist one by one.
                http://www.balaboss.com/faq_installation.htm   
Excerpt:
How do I reference the BalaBoss.mdw workgroup in the command line?
In the default BalaBoss Client Navigator installation, the following command line is associated with launching the BalaBoss Client Navigator application:

"C:\Program Files\BalaBoss\BalaBoss.mde"

The above command line assumes

 You have joined the BalaBoss workgroup (and therefore made BalaBoss.mdw your default workgroup), and
 The "MDE extension was successfully associated with MSAccess.exe during the installation process.

There are a variety of circumstances in which the above default may not be suitable for your particular workstation:

For example:

 You may use MSAccess.exe for other applications and you may not want the BalaBoss workgroup file to constitute your default security, or
 The "MDE extension may be associated with an application other than MSAccess.exe. In some circumstances the installation of Maximizer will cause "MDE to be associated with that application.

Under any such circumstances we suggest that you launch BalaBoss Client Navigator by using a more explicit command line:


0
sanderrobAuthor Commented:
Just thought I would update this.

We have had no success at this point, even with the assistance of the developers.
0
puppydogbuddyCommented:
You should have posted back sooner.  It sounds like you need to update your access  or jet  service packs.   See this link:    http://kbalertz.com/829558/Information-about-Service.aspx

Excerpt:
Additionally, Jet 4.0 Service Pack 8 fixes the following past problems:
Performance problems occurred when certain pass-through queries were run.
Microsoft Access unexpectedly quit when you tried to upsize a database where the tables contained triggers.

Note This service pack prevents Access from quitting. This service pack does not make it possible for you to upsize tables with triggers.
An "Invalid argument" error message occurred when you tried to create a linked table by using DAO code after the installation of Jet 4.0 Service Pack 7.
An access violation occurred when you ran certain queries that used linked Paradox tables.
Oracle integer field appeared as double in Access.
When you tried to create links to dBase files, you received an access violation or nothing occurred. That is, no link was created, and you did not receive an error message.
When you refreshed a linked table, you were prompted to select a DSN although you were still using the same DSN, and all the connection information was correct.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.