access 2007 datafile (.mdb) and access 2003 runtime problem?

[babybleu]

Can someone please help me? I'm new to this tech stuff as I've had someone
else handle it for the past 10 years. I'm a little out of the loop!!! LOL
I've just upgraded all of my computers to MS Home, Office and Student 2007
except for the main server which has MS Enterprize which included Access
2007. My backup data file has been converted to Access 2007 and the full
program is working (kinda) on the server, for the first time in a month.
(this has been a real nightmate.) The software supplier won't give me much
help because I'm not paying $125.00 for support for a program I've had since
1998. However, when I try to link the other computers on the network to the
data file on the server, it says that it cannot link to the file. The
program I'm using has been loaded on the other network computers and it
includes a Access 2003 runtime program. My computer guy is saying that I
have to buy a new 2007 access program to get to it. Is there any other way
to get around this? I've already spent too much money on this update. If I
convert the 2007 back to the 2003 version would that work?

 

[babybleu]

I just found out that MS Access 2007 runtime is available for a free
download. Would this work to download that to all of the workstations on the
network since I have the full program on the main server?

 

[Douglas J. Steele]

That's exactly what it's intended for.

 

[babybleu]

Doug, I downloaded the 2007 runtime and I still can't get it to come up on
the other workstations. I'm also having a problem on the main server with
the data file, (I think) My font end program has a security area that you can
enable different areas for users. If I give full permissions, some areas
still aren't accessible. I really wish that the software company would just
remotely fix everything for me but they're not very cooperative since I
cancelled monthly support last October after 10 years.

 

[Douglas J. Steele]

What does "can't get it to come up on the other workstations" mean?

Has the database been split into a front-end (containing the queries, forms,
reports, macros and modules), linked to a back-end (containing the tables
and relations)? Is the front-end installed on the user's workstation? Has
the folder where the front-end is installed been set as a Trusted Location?

 

[babybleu]

I'm not sure if I'm explaining this right at all. I have a program for
flooring companies that is called Floors for Windows. It uses MS Access for
it's database. I didn't know there were front end and back end areas of this
at all. I've been running this program for about 10 years now but had
someone else that was my "IT" guy doing the technical stuff. I've loaded the
program (Floors) and followed the suppliers directions. I can look at the
data file in MS Access on my main server and the program runs, somewhat,
there are problems with a JET something or other, another problem with a VBD
or something like that, so it's not running smoothly, but running. I've
loaded the program to the other workstations and when I point to the data
file from the server on the network, it says it can't link to the data file.
The software company is using Access 2003 and I believe that a runtime of
that is included with the program. Today, I copied the data file and brought
it up, converted, to the main server and it popped into the program and
really screwed things up. I think I'm going to just pay the stupid company
their $125.00 a month for support so I don't go absolutely nuts trying to
figure it out. I'm not stupid but I think that this is way deep for my
skills.