This is definitely the wrong mailing list to post this on.
Try some of the Microsoft sites
Microsoft Universal Data Access
http://www.microsoft.com/data/
MS Developer Network
http://www.microsoft.com/data/
I know nothing about the jet engine. But I would suspect what you are seeing
is a difference between the jet engines in Access 97 and access 2000. I
suggest you look for a "compatibility mode" setting of some sort and review
the locking changes. Microsoft also have a product called MSDE which is a
cut down version of SQLServer which you can apparently distribute if you are
using MSdevelopment tools. You might look at using this.
Adam
----- Original Message -----
From: "Peter Milsom" <peterm@milsom.co.nz>
To: <adsl@unixathome.org>; "'Aaron Martin'" <aaronm@firesecurity.co.nz>
Sent: Thursday, October 05, 2000 8:40 AM
Subject: RE: MW1122 and arron martins' query
> This is somewhat off your topic but your problems with Terminal Server
> bring to mind an excruciating experience we've just been through.
>
> A "seemingly" straight forward (famous last words) conversion from
> Winframe 1.8 to Metaframe over Terminal Server turned to a 2 week
> custard wallow for us the application providers.
>
> Our Access 97 application on Winframe 1.8 ran very well. 15 uses and
> reasonable service. The conversion to 2000 runs well on local area
> network and tested OK at low volumes(mark that slip) on
> Metaframe/Terminal Server. We had adopted all the tuning and set up
> suggestions published plus some experience we had picked up as the
> guardians of the Winframe site.
>
> Once live - Holy H$#@. Unbelievable locking with the Jet engine
> stopping processes because of contention on the database followed by
> data corruptions. No reference to any such problems on either the
> Citrix or Microsoft sites. After two weeks struggling with intermittent
> and difficult to repeat errors we capitulated and went back to Winframe.
> This is such a biggie there must surely be other experiences like ours.
> Any suggestions for other web sites, use groups forums where the
> unfortunate can share??
>
> Thanks
>
>
> Peter Milsom
>
> -----Original Message-----
> From: Aaron Martin [mailto:aaronm@firesecurity.co.nz]
> Sent: Wednesday, 4 October 2000 12:48 p.m.
> To: 'adsl@unixathome.org'
> Subject: MW1122
>
> Well I got my MW1122 installed in auckland branch, however there seems
> to be
> a problem.
>
> It is faster, about 20% increase both ways. The problem is with
> interactive
> connections i.e. Terminal Server. If a client stays idle too long they
> get
> disconnected from the server, without any error except that "The
> Terminal
> Server has ended the connection". However at the server end it thinks
> that
> the connection is still active. This never happened when we were using
> an
> M10, and I have made no others changes apart from using an MW1122
> instead of
> the M10.
>
> Does anyone have any ideas on this?
>
>
> p.s. An anonymous telecom installer told me that the MW1122 has known
> bugs
> / problems, but Telecom has released it anyway. Apparently alot of the
> MW1122 modems have been recalled due to these problems...
>
> This message is part of the NZ Broadband mailing list.
> see http://unixathome.org/adsl/ for archives, FAQ,
> and various documents.
> To unsubscribe: send mail to majordomo@unixathome.org
> with "unsubscribe adsl" in the body of the message
>
> This message is part of the NZ Broadband mailing list.
> see http://unixathome.org/adsl/ for archives, FAQ,
> and various documents.
> To unsubscribe: send mail to majordomo@unixathome.org
> with "unsubscribe adsl" in the body of the message
>
This message is part of the NZ Broadband mailing list.
see http://unixathome.org/adsl/ for archives, FAQ,
and various documents.
To unsubscribe: send mail to majordomo@unixathome.org
with "unsubscribe adsl" in the body of the message
Received on Thu Oct 5 09:49:04 2000