• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 448
  • Last Modified:

Batch File

Hello,

One part of our product currently runs on Access 97 (it has to as it breaks in Access 2000 or above).  I am currently trying to get it to run on Windows 7.  I loaded and am running Access 97 in compatibility mode and the vast majority of the product launches and runs just fine.  I have one batch file that launches an overnight process and it runs automatically (i.e. the application launches and runs without user intervention).  Every time I launch the batch file, I get a message that comes up and says "Invalid Access Version".  Here is a copy of the batch file:

"C:\Program Files\Microsoft Office97\Office\Msaccess.exe" "%AppPath%\Application\Posservr\SBpgmEOD.MDE" /cmd Auto

Thank you in advance for your help!
0
RyanEmporos
Asked:
RyanEmporos
  • 7
  • 5
  • 5
1 Solution
 
Jeffrey CoachmanCommented:
Win7, 32 or 64 bit?

I don't think Access 97 will even run on Win 7, 64 bit.
0
 
Jeffrey CoachmanCommented:
<One part of our product currently runs on Access 97 (it has to as it breaks in Access 2000 or above)>
No offense, ...but did you ever investigate why?
0
 
RyanEmporosAuthor Commented:
Thank you for your response boag2000.  We are currently trying our applications out on Windows 7 Ultimate 32-bit.  If we can get everything to run on my test bed, we'll probably start deploying Windows 7 Professional 32-bit.  As far as investigating why the component I'm trying to use breaks in Access 2000 and above, the programmers said something about Microsoft restricting the number of objects allowed in the MS Jet database engine (which Access uses) starting in Access 2000 so people would be forced to use MS SQL Server.
0
Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

 
Jeffrey CoachmanCommented:
I have never heard of any such limitations.
There are lots of people here still running Access 97 without any of these limits.
In fact, the number of Database objects allowed has "Increased" since Access 97.


In any event, running Access 97 under Win 7 may be pushing the limits of compatibility.

I would only try running apps in OS' going back 2 versions.
Access 97 was released over 11 years.
:-O

So at the very least, Access 97 is 4 office versions behind, and 4 Operating systems behind.
;-)

Perhaps there is an easy fix  for this.

Let's see what some other Experts say...

;-)

JeffCoachman
0
 
RyanEmporosAuthor Commented:
Thank you again for the info.  One additional piece of info is I can get the app to launch correctly if I use the following command:

"C:\Program Files\Access 97 Runtime\Msaccess.exe" /runtime /excl  /wrkgrp "C:\System.mdw" "C:\APPDIR\POSServr\SBPgmEOD.mde"

The only thing is since it's an End-of-Day program, it needs to run automatically.  When I use the above command, it brings up the program, but it doesn't automatically run.  The batch file is supposed to make it run automatically.

One other note, I understand that the batch file is calling for full Access to run and the command I pasted to this comment is calling up Access Runtime.  I have a batch file for both full Access and Access Runtime, and they both come up with the same "Invalid Access Version" error.
0
 
Helen FeddemaCommented:
Since no one else has said the obvious, I will -- why not upgrade to at least Office 2003 (better, Office 2007)?
0
 
RyanEmporosAuthor Commented:
Thank you for your comment Helen.  The application breaks when run in Access 2000 and above.  Upgrading to a newer version of Access is simply not an option.
0
 
Helen FeddemaCommented:
To help in the transition, here is a list of some of the code changes that might be needed:

Updating-a-Database.doc
0
 
Helen FeddemaCommented:
It might be a necessity at some point, especially since you are upgrading the OS.
0
 
RyanEmporosAuthor Commented:
Thank you for the info!  I'll read it and try it out.
0
 
Helen FeddemaCommented:
But I know how it is with some companies -- I am currently doing some work for a major (world-wide) company that is still using Office 2000.
0
 
Helen FeddemaCommented:
That info is only good for upgrading to a higher version.
0
 
RyanEmporosAuthor Commented:
We're actually in the middle of redeveloping our product from the ground up.  I am trying to squeeze a little more life out of our current product while our new product is being developed.
0
 
RyanEmporosAuthor Commented:
I got the batch file to work!  Here is a copy of it:

"C:\Program Files\Access 97 Runtime\Msaccess.exe" /runtime /excl  /wrkgrp "C:\System.mdw" "C:\AppDir\POSServr\SBPgmEOD.mde"  /cmd Auto

It now fires off the .mde and auto executes it.  For some reason, when it was calling full blown Access, it didn't like it.  Now it calls Access Runtime and runs like a champ.

Thank you everyone for your input.
0
 
Jeffrey CoachmanCommented:
Are you *sure* you want to run the DB with the runtime option?
0
 
RyanEmporosAuthor Commented:
Yes.  The DB is a .MDE so it's basically an executable.  It is an End-of-Day process that is designed to automatically run with no user intervention.  So basically, all we need it to do is launch at a predetermined time in the middle of the night, run, and close itself out which is what it is doing.
0
 
Jeffrey CoachmanCommented:
OK
;-)
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 7
  • 5
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now