I'm setting up a project for a client on a new Windows Terminal
Server. The application is currently in A2K, but the sysadmin does
not want to install that, he wants to install A2K3, because Office
2K3 is the organization's new standard (they want to be fully
converted within the new calendar year).

What issues will I have, if any, with A2K3 on WTS? Anything
different from A2K? Anything not specific to WTS that I need to know
about A2K3, which I've never used, ever?

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

On Wed, 29 Dec 2004 22:53:45 GMT, "David W. Fenton"
<dXXXfenton (AT) bway (DOT) net.invalid> wrote:

So far I am impressed with the Access 2000 compatibility mode in
Access 2003.

-Tom.

David W. Fenton wrote:
David,

I've had great success with that particular setup. I develop in A2K,
but one client in particular has been running an A2K FE/A2K BE using
A2K3 on WTS and haven't come across any major problems in over 2 years.
Well, except that I keep forgetting the workgroup administrator is
accessed via Tools|Security and not from a separate program. I like
the fact that A2K3 opens an A2K db and allows new queries, reports,
etc. without having to convert the db.

I have had to make table changes over time via VBA (adding tables with
appropriate security, adding fields, modifying fields) and haven't run
into any issues there once it passed testing on my A2K development
machine. All coding currently in my application has worked fine. BTW,
I still use DAO rather than ADO.

There is still the rare crash/corruption, but that has dropped
dramatically since I convinced them to put the BE on the TServer as
well as the FE. (That was due to intermittent network hiccups that
they never fully resolved, but they only seemed to affect Access
databases.) And when A2K3 does a repair, it makes a copy prior to
running the repair. A nice feature, but I had already learned the hard
way to always make a backup first. (Thanks, Peter Miller.)

I haven't found a case for A2K3 over A2K in my situation, but at least
they work and play very well together.

Tom van Stiphout <no.spam.tom7744 (AT) cox (DOT) net> wrote in
newsfv6t01kovm7mr0dq8lcjcf7oqcqdero30 (AT) 4ax (DOT) com:

What does that mean?

Can I set it from code?

Can I configure the WTS users to run in A2K compatibility mode
without logging on as each one?

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

On Thu, 30 Dec 2004 22:55:30 GMT, "David W. Fenton"
<dXXXfenton (AT) bway (DOT) net.invalid> wrote:

What I meant was, that running an Access2000 application in Access2003
is entirely seamless. No need to set anything. Just really good
backward compatibility from your friends at MSFT.

-Tom.

Tom van Stiphout <no.spam.tom7744 (AT) cox (DOT) net> wrote in
news:q4f9t01403gjqic3mkog9l5ptlur3nlapb (AT) 4ax (DOT) com:

What about the code signing thing? Don't you have to turn something
off in Access to get it to stop nagging you about unsafe code
execution?

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

David W. Fenton wrote:
Set Macro Security to Low, just like in Word/Excel.

--
This sig left intentionally blank

Trevor Best <nospam (AT) besty (DOT) org.uk> wrote in
news:41d600c6$0$21321$db0fefd9 (AT) news (DOT) zen.co.uk:

Where? Can it be done in code? Can the base installation of Access
be configured this way so that all users inherit that setting when
they log on for the first time?

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

I've been following this thread, and was going to ask the same question, but
then I thought ... "Now how secure would that be if you could turn off the
security that prevents you running the database (without a message) from the
database?" ...

Darryl Kerkeslager


"David W. Fenton" <dXXXfenton (AT) bway (DOT) net.invalid> wrote:

David W. Fenton wrote:
I've not tried, I've not looked at 2003 in depth yet.


--
This sig left intentionally blank