Access 97 on a Windows 2003 server

#1

I can install Access 97 and create or open a database without a
problem. However, as soon as I attempt to open any form Access
crashes. This isn't a problem with my Access 97 applicationas it works
in other environments and also if I attempt to create the simplest
possible Access database in the Windows 2003 environment with one
form then as soon as I attempt to open the form the problem is
replicated.

I have searched for a solution and all I come with is others with the
same problem but no solution.

Does anyone have any idea how this issue can be resolved?

Thanks
Jon

#2

<jon (AT) norchard (DOT) com> wrote

Quote:

I can install Access 97 and create or open a database without a
problem. However, as soon as I attempt to open any form Access
crashes. This isn't a problem with my Access 97 applicationas it works
in other environments and also if I attempt to create the simplest
possible Access database in the Windows 2003 environment with one
form then as soon as I attempt to open the form the problem is
replicated.

I have searched for a solution and all I come with is others with the
same problem but no solution.

Does anyone have any idea how this issue can be resolved?

Thanks
Jon

Are you trying to run Access97 on the server, or only user the 2003 server
to store the backend db?
Access97 requires full rights to the system32 folder with can be a problem
on a server.
You don't need Access on the server if you only need the server to store the
backend.

IMO: Never run Access on a server. It can be a resource hog and because of
it's age, Access97 (with I use) may cause the server to crash when it does.

#3

On Jan 15, 1:11*pm, "paii, Ron" <n... (AT) no (DOT) com> wrote:

Quote:

j... (AT) norchard (DOT) com> wrote in message

news:56d94527-46d1-42bc-b22c-dfda7ae447bb (AT) t39g2000prh (DOT) googlegroups.com...

I can install Access 97 and create or open a database without a
problem. However, as soon as I attempt to open any form Access
crashes. This isn't a problem with my Access 97 applicationas it works
in other environments and also if I attempt to create the simplest
possible Access *database in the Windows 2003 environment with one
form then as soon as I attempt to open the form the problem is
replicated.

I have searched for a solution and all I come with is others with the
same problem but no solution.

Does anyone have any idea how this issue can be resolved?

Thanks
Jon

Are you trying to run Access97 on the server, or only user the 2003 server
to store the backend db?
Access97 requires full rights to the system32 folder with can be a problem
on a server.
You don't need Access on the server if you only need the server to store the
backend.

IMO: Never run Access on a server. It can be a resource hog and because of
it's age, Access97 (with I use) may cause the server to crash when it does.

Thanks Ron,

Possibly a bit out of my depth on this but what I'm attempting to do
is give some users the ability to use an existing Access 97 database
via a web browser. Their ultimate requirement is that no software is
installed to any PC's and they just have to type in a URL to access.
The database is split into FE and BE with the FE usually resident on
individual PC's and the BE on a network server. I'm simply trying to
get the application to work on the server and then will probably give
access via Citrix. I think I've got a steep learning curve coming up!

Regards
Jon

#4

On Thu, 15 Jan 2009 05:26:25 -0800, jon (AT) norchard (DOT) com wrote:

Quote:

Thanks Ron,

Possibly a bit out of my depth on this but what I'm attempting to do is
give some users the ability to use an existing Access 97 database via a
web browser. Their ultimate requirement is that no software is installed
to any PC's and they just have to type in a URL to access. The database
is split into FE and BE with the FE usually resident on individual PC's
and the BE on a network server. I'm simply trying to get the application
to work on the server and then will probably give access via Citrix. I
think I've got a steep learning curve coming up!

I have not seen what you are seeing, but when our A97 terminal servers
were upgraded from NT4 to WinServer 2003 we had to ultimately change to a
newer version of Access because of resource problems.

There is an issue with A97 that a low priority thread always makes it
look like it is using nearly all of the PC. Since the priority is low
this was more of a perception problem, than an actual one. On WinServer
2003 it appears to become a *real* problem. Once we switched to a newer
version of Access that issue was resolved.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

#5

<jon (AT) norchard (DOT) com> wrote

On Jan 15, 1:11 pm, "paii, Ron" <n... (AT) no (DOT) com> wrote:

Quote:

j... (AT) norchard (DOT) com> wrote in message

news:56d94527-46d1-42bc-b22c-dfda7ae447bb (AT) t39g2000prh (DOT) googlegroups.com...

I can install Access 97 and create or open a database without a
problem. However, as soon as I attempt to open any form Access
crashes. This isn't a problem with my Access 97 applicationas it works
in other environments and also if I attempt to create the simplest
possible Access database in the Windows 2003 environment with one
form then as soon as I attempt to open the form the problem is
replicated.

I have searched for a solution and all I come with is others with the
same problem but no solution.

Does anyone have any idea how this issue can be resolved?

Thanks
Jon

Are you trying to run Access97 on the server, or only user the 2003 server
to store the backend db?
Access97 requires full rights to the system32 folder with can be a problem
on a server.
You don't need Access on the server if you only need the server to store
the
backend.

IMO: Never run Access on a server. It can be a resource hog and because of
it's age, Access97 (with I use) may cause the server to crash when it
does.

Quote:

Thanks Ron,

Possibly a bit out of my depth on this but what I'm attempting to do
is give some users the ability to use an existing Access 97 database
via a web browser. Their ultimate requirement is that no software is
installed to any PC's and they just have to type in a URL to access.
The database is split into FE and BE with the FE usually resident on
individual PC's and the BE on a network server. I'm simply trying to
get the application to work on the server and then will probably give
access via Citrix. I think I've got a steep learning curve coming up!

Regards
Jon

I should have excluded terminal server. But you will need more memory than
you may expect.

I am running Access97 on a Windows 2000 server with Citrix 2000.
To get A97 to run on that system, I needed to add a group with full rights
to system32, then assign users to that group. Even the Administrator user
will not function without this group membership. Also download compatibility
documents from Microsoft. If I was setting an application up today, I would
consider a new version of Access with runtime on the server.

#6

"David W. Fenton" <XXXusenet (AT) dfenton (DOT) com.invalid> wrote

Quote:

"paii, Ron" <none (AT) no (DOT) com> wrote in
news:gknlv3$1gn$1 (AT) news (DOT) motzarella.org:

I am running Access97 on a Windows 2000 server with Citrix 2000.
To get A97 to run on that system, I needed to add a group with
full rights to system32, then assign users to that group. Even the
Administrator user will not function without this group
membership. Also download compatibility documents from Microsoft.

That's very strange. I ran A97 on a Win2K terminal server for
programming purposes (in an admin logon) for years without any
changes to the default permissions.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

I found it strange also, but after working with Microsoft email support for
2 weeks that is what made it run. It had been running on NT4 for 3 years
before without a problem. My system may be unique, but it was after a clean
install of Windows Server 2000 and Citrix for Windows 2000.

#7

"paii, Ron" <none (AT) no (DOT) com> wrote:

Quote:

IMO: Never run Access on a server. It can be a resource hog

I have a client running A2003 runtime on a Windows 2008 Terminal Server just fine.

Quote:

and because of
it's age, Access97 (with I use) may cause the server to crash when it does.

It might have other problems but for A97 to crash a server? I wouldn't think so.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

#8

"David W. Fenton" <XXXusenet (AT) dfenton (DOT) com.invalid> wrote

Quote:

"paii, Ron" <none (AT) no (DOT) com> wrote in
news:gkodds$7o6$1 (AT) news (DOT) motzarella.org:

"David W. Fenton" <XXXusenet (AT) dfenton (DOT) com.invalid> wrote in message
news:Xns9B9492028FD24f99a49ed1d0c49c5bbb2 (AT) 74 (DOT) 209.136.99...
"paii, Ron" <none (AT) no (DOT) com> wrote in
news:gknlv3$1gn$1 (AT) news (DOT) motzarella.org:

I am running Access97 on a Windows 2000 server with Citrix
2000. To get A97 to run on that system, I needed to add a group
with full rights to system32, then assign users to that group.
Even the Administrator user will not function without this
group membership. Also download compatibility documents from
Microsoft.

That's very strange. I ran A97 on a Win2K terminal server for
programming purposes (in an admin logon) for years without any
changes to the default permissions.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

I found it strange also, but after working with Microsoft email
support for 2 weeks that is what made it run. It had been running
on NT4 for 3 years before without a problem. My system may be
unique, but it was after a clean install of Windows Server 2000
and Citrix for Windows 2000.

Was the NT4 box upgraded to Win2K? Or was it a different box, or a
clean install of Win2K?

Also, I was not using Citrix, but just WTS. That oughtn't have
anything at all to do with how an application runs, though.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

It was a clean install onto new drives on the original NT4 box.

#9

"Tony Toews [MVP]" <ttoews (AT) telusplanet (DOT) net> wrote

Quote:

"paii, Ron" <none (AT) no (DOT) com> wrote:

IMO: Never run Access on a server. It can be a resource hog

I have a client running A2003 runtime on a Windows 2008 Terminal Server
just fine.

I should have excluded Terminal Server. I assumed the OP was talking about a
file server.

Quote:

and because of
it's age, Access97 (with I use) may cause the server to crash when it
does.

It might have other problems but for A97 to crash a server? I wouldn't
think so.

A97 was released on the old Windows98 days. I would expect it uses some low
level calls that a modern application would not. In general I like to
protect my servers and IMO running any workstation applications on a serve
increases the likelihood of server downtime.

I would't expect the server version of a print driver to crash a server, but
I had one that did. It was running at the operating system level.

Quote:

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

#10

"paii, Ron" <none (AT) no (DOT) com> wrote:

Quote:

I would't expect the server version of a print driver to crash a server, but
I had one that did. It was running at the operating system level.

Printer drivers run at a very different level in the OS than do apps.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/