Access97 and win 2003 server

[Guest]

Hi, all!

Does any body know Access97 could be hosted on win 2003 server (std edition,
sp1)?

We have an application using Access 97, and it did not lauch well when we
moved it to the new server.

Access 97 itseft was installed fine, but it failed to start any app, new or
existing. The event viewer just said application failed, or app hang.

Thanks!

 

[Douglas J Steele]

I've heard of problems running Access 97 on Windows 2003, but I have no
specifics.

However, what is it you're trying to do? If all you're doing is putting the
MDB on the server, you shouldn't even require that Access be installled:
users connecting to the MDB file will launch Access on their workstation.

 

[Guest]

Thank you for your reply!

My vb6 application uses access 97 to process access reports and
print/fax/email them out.

The app is running from the server as a console app with no gui to user. If
I cannot figure out where is the conflict between them, I have to 1) convert
acc97 to later version, or 2) move to another server (we have xp running
acc97).

On 1), I am afraid the object model has changed from acc97 to acc03, and lot
of my code has to be reworked. For instance, does report object in the newer
version has PrtDevName, PrtDevMode, or Caption properties? etc.

 

[Douglas J Steele]

Don't have Access 2003 installed here, but looking on MSDN
(http://msdn.microsoft.com/library, look in Office Solutions Development |
Microsoft Office 2003 | Office 2003 | VBA Language Reference | Microsoft
Access Visual Basic Reference | Reference) I don't see any of those three
properties. However, working with printers is definitely easier in Access
2003, as it exposes a Printer object (and a Printers collection), just as VB
does.

 

[Guest]

Is the vb6 application associated with a user? does that
user have a printer installed?

If the vb6 application is not associated with a user, does
the default system context have a printer installed?

It is difficult to use Access without a GUI user, because
all of the error messages go to the gui, causing the application
to hang waiting for the OK button if there is no gui. For
these reason, it may be better to run the application as a
logged in user (with a companion application to press
the 'ok' button any time it comes up).

(david)