Re: ADO/MDAC on Terminal Server

From: William \(Bill\) Vaughn (billvaRemoveThis_at_nwlink.com)
Date: 04/01/04 

Date: Thu, 1 Apr 2004 10:39:17 -0800

It sounds like a nightmare. Given the nature (and behavior) of JET, I'm
surprised it works at all.
If I were you I would get rid of JET completely and code the application to
access SQL Server directly.

I hope you get it working... 

-- 
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"PaulJS" <anonymous@discussions.microsoft.com> wrote in message
news:80D86C21-513F-4DD6-A86A-B66C280BF00B@microsoft.com...
> Greetings!
>
> Our company took over a competitor, which necessitated upgrading MS Access
XP database system to SQL Server 2000.  However, we are still using MS
Access as the front end to SQL Server.  (Note: The Access front end is still
an MDB file, not an Access Project file type.)  Our new division's users are
accessing the database system via a Windows 2000 Terminal Server which is
also running Citrix MetaFrame on top of Terminal Services.  The MS Access XP
front end is running on the Terminal Server (via Citrix).  The new users use
this Access front end for their data operations.
>
> We've gotten past most problems, except these: 1) Whenever we change the
MDB file due to fixes and modifications, the system "errors" whenever it
hits the code that tries to open up an ADO connection, displaying a "Cannot
open connection" or "invalid in this context" message.  Strangely, if I log
in to Citrix, (I'm an Administrator), I get no error, but any other users
cannot get past the error.  We upgraded MDAC to 2.8 prior to putting the
database front end on the Terminal Server.  Previously, the Access front end
only used DAO, no ADO.  However, with the upsizing to SQL Server, ADO has
some advantages.  (Other info: We made sure we were in "Install" mode before
installing MDAC 2.8.  Also, the very same MS Access XP front end MDB file,
including new ADO code, runs perfectly on local user machines that access
the database over the LAN, i.e., not using Terminal Services/Citrix.  In
these instances, the Access XP front end file is running on each user's
machine.)
>
> The second issue is related, but not as critical as #1.  Whenever a
regular user, (NOT an Admin), accesses the MS Access front end over the
Terminal Server following an upgrade of the MDB file, the user gets a
"missing reference" error as the MDB file opens up.  Our "fix" is to simply
go into the References selection list box in the VBA window, deselect a
random reference, close the list box, then reopen it and select the
reference again.  The user is now able to go in.  Notes: None of the
references are flagged as MISSING in spite of the error.  They are all
there.  All we do is randomly pick one of the references, like "Windows
Common Controls", deselect it, save the change, then open References list
box again and reselect the reference just removed.  It seems to reset
something that now allows a user into the system.
>
> Thanks for reading this saga.  If I haven't explained it too well, just
let me know and I'll provide better details.
>
> Thank you,
> P

Relevant Pages

  • Re: newbie problem: updating an access db
    ... modifying the code to use SQL Server it still exhibited the same ... changed the path to the supplied access .mdb file in the web.config ... the delete and update commands, so now they just test whether Adnum= ?. ... get this code to work, I don't want to start modifying it to use MSSQL, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Recurring import of linked text file data
    ... indication that the amount of data being imported was exceeding ... calculate how much time you have before you would hit my arbitrary size. ... The mdb file was about 256mb, ... migrate it to SQL Server 2000. ...
    (microsoft.public.access.externaldata)
  • Re: Desktop SQL Server
    ... It's also hard to provide you with a better reference because you didn't ... uninstalled when the SQL server is installed. ... Server but, according to my reading on this, the Microsoft Jet Engine ... who runs an application that uses the SQL Server will have to uninstall ...
    (microsoft.public.access.externaldata)
  • Re: VBA vs VB.net for Access application
    ... wants people to use SQL Server? ... You mean accessing data in a mdb file? ... ms-access, or vb.net to read and write data in a mdb file... ... As to using visual studio, ...
    (microsoft.public.access.modulesdaovba)
  • Re: From VB .Net, how obtain ref to Access project?
    ... Brendan Reynolds ... > same/similar commands available in Access VBA. ... > get the commands to talk to the approrpiate .mdb file. ... >>> can I obtain a reference to a database file created in Access? ...
    (microsoft.public.access.tablesdbdesign)
Loading