Re: client side

From: Andrea Montanari (andrea.sqlDMO_at_virgilio.it)
Date: 05/18/04

  • Next message: Ryan Columbus: "Constant Disk Activity" 
    Date: Tue, 18 May 2004 22:46:45 +0200

    hi Steve,
    "steve" <anonymous@discussions.microsoft.com> ha scritto nel messaggio
    news:8EBB34FC-64EC-4B21-9221-73CDECEF9DC0@microsoft.com...
    > First - thank you for the replies.
    >
    > I am at a loss then what it is that he needs. MSDE 2000 SRa is installed
    on a Windows 2000
    > Advanced Server that I set up for this. He then installed the database
    onto that computer and I created
    > a VPN so he could use his Enterprise Tools remotely to make some
    configuration changes. The
    > application that interfaces with it he built on a VB / Access97 platform.
    He said the client side was
    > needed to link the application to the MSDE server and that he was having
    trouble linking it but that
    > they were some other ways he could try. His suggestion was that I install
    the "client side" items on the
    > workstation that was going to be running the VB / Access97 user interface.
    While I am MS certified,
    > in prior jobs I haven't worked much with SQL server at the installation
    phase but have rather supported
    > the interfaces after they were written and installed by the programers. I
    apologize for my lack of
    > understanding and use of wrong syntax. We've used this programmer for
    years and everything else
    > he has done has been sucessful. Perhaps he isn't able to explain what it
    is that he wants.

    usually, at client side, you shoul'd only install MDAC that provides the
    client side dirvers and interfaces to connect to remote SQL Server/MSDE
    instances...
    what your guy intended is not wrong at all, becouse he indicates to install
    the Client Components for SQL Server, that includes MDAC and the whole tools
    as Enterprise Manager, Query Analyzer and so on to manage SQL Server
    instances.. this is fine as long as you own a full SQL Server edition that
    license you to do it, while MSDE only provides a server side setup with no
    management tools bu oSql.exe, a command line tool
    (http://support.microsoft.com/default.aspx?scid=kb;EN-US;q325003)
    you reported the client application is a VB / Access97 platform... then you
    are only required to install VB/Access runtime dependencies and MDAC on the
    clients.... or just VB/Access runtime dependencies on the server... as long
    as the app =;-) 

    -- 
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtm        http://italy.mvps.org
DbaMgr2k ver 0.7.0  -  DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
--------- remove DMO to reply
  • Next message: Ryan Columbus: "Constant Disk Activity"

    Relevant Pages

    • Re: Any help here???
      ... > start looking for things that are non standard (like having MDAC installed). ... > Format your drive, do a new/clean install of XP, and go from there. ... >>> data provider is optimized for SQL Server. ... >>> I've never had any SQL Server connectivity problems since I've switch to ...
      (microsoft.public.dotnet.framework.aspnet)
    • Re: Help Please Wit Error
      ... Occasionally I receive the error you are mentioning when the SQL Server ... I have had to completely remove the MDAC and re-install it as well ... see an example of the connection string you are using. ... Please install Microsoft Data Access Components ...
      (microsoft.public.dotnet.csharp.general)
    • Re: SQL Server Native Client is not supported on the current proce
      ... I unselect the Client tools so that it will uninstall. ... When you open Programs and Features in CP, click on the Microsoft SQL Server ... either install SQL Server 2008 Client Components on a different ...
      (microsoft.public.sqlserver.setup)
    • Re: Any help here???
      ... Well, for starters, I believe MDAC is unnecessary for .NET applications - as ... ADO.NET has its own SQL Server provider for data access. ... > trust me - all that's been done here was to install SP2 or upgrade of XP ...
      (microsoft.public.dotnet.framework.aspnet)
    • Re: SQL Server 2005 Express OLEDB Connection from VB6
      ... Thanks for getting me to read this again and realizing they meant the client ... I think we'll stick with ODBC, since there is less to install on the client ... Microsoft SQL Server Native Client ...
      (microsoft.public.sqlserver.connect)