DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 4 of 4

Thread: Second Request: Linked Tables

Hybrid View

  1. #1
    Al Meadows Guest

    Second Request: Linked Tables

    I have an Access database setting on one of the servers which uses a FILE
    DSN to connect to a large number of SQL Server files.

    Using VB and Access and VBA with XL I have no trouble creating queries or
    accessing both the Access based tables or the linked SQL tables.

    Now I am trying to do the same thing with ASP pages using VB Script. I
    created a SYSTEM DSN connection to the Access Database and accessing the
    Access tables works fine. When I try to access or link to one of the
    linked tables then I get an error which refers to the FILE DSN that the
    database uses and it doesn't work.

    I tried creating a SYSTEM DSN for the Access Database to use to link to the
    SQL data but this didn't help.



  2. #2
    mike Guest

    Re: Second Request: Linked Tables


    Why not just connect directly to the SQL Server tables and bypass the access
    link tables?



    "Al Meadows" <fineware@fineware.com> wrote:
    >I have an Access database setting on one of the servers which uses a FILE
    >DSN to connect to a large number of SQL Server files.
    >
    >Using VB and Access and VBA with XL I have no trouble creating queries or
    >accessing both the Access based tables or the linked SQL tables.
    >
    >Now I am trying to do the same thing with ASP pages using VB Script. I
    >created a SYSTEM DSN connection to the Access Database and accessing the
    >Access tables works fine. When I try to access or link to one of the
    >linked tables then I get an error which refers to the FILE DSN that the
    >database uses and it doesn't work.
    >
    >I tried creating a SYSTEM DSN for the Access Database to use to link to

    the
    >SQL data but this didn't help.
    >
    >



  3. #3
    Al Meadows Guest

    Re: Second Request: Linked Tables

    Because I create JOINS between the tables for queries. The SQL is a 3rd
    party database product where I don't want to add tables that are not part of
    the base product. We keep our own summary and external tables in Access. I
    use them in VB and Access daily. Why not via ASP?


    mike <michael.viglianco@bankofamerica.com> wrote in message
    news:39a16233$1@news.devx.com...
    >
    > Why not just connect directly to the SQL Server tables and bypass the

    access
    > link tables?
    >
    >
    >
    > "Al Meadows" <fineware@fineware.com> wrote:
    > >I have an Access database setting on one of the servers which uses a FILE
    > >DSN to connect to a large number of SQL Server files.
    > >
    > >Using VB and Access and VBA with XL I have no trouble creating queries or
    > >accessing both the Access based tables or the linked SQL tables.
    > >
    > >Now I am trying to do the same thing with ASP pages using VB Script. I
    > >created a SYSTEM DSN connection to the Access Database and accessing the
    > >Access tables works fine. When I try to access or link to one of the
    > >linked tables then I get an error which refers to the FILE DSN that the
    > >database uses and it doesn't work.
    > >
    > >I tried creating a SYSTEM DSN for the Access Database to use to link to

    > the
    > >SQL data but this didn't help.
    > >
    > >

    >




  4. #4
    Steve Guest

    Re: Second Request: Linked Tables


    Do your linked SQL tables require a password to connect and have you set that
    up correctly in Access? (i.e. if you get prompted for a password from your
    VB app or in Access, then this explains why you are not getting to the tables
    via ASP)

    Have you moved your database recently?
    (i.e. you linked tables may require relinking; you client connectivity should
    be tested against this new location)

    Is your webserver is the same network location as your VB application?
    (i.e. client-side access might be a good tale-teller in this case. The ASP
    pages and the VB apps are considered clients of your database. Security
    due to network client location could be at fault.)

    Have you attempted to connect to the Access Database via a connection string
    rather than a DSN?
    (i.e. I've found that using a connection string rather than a DSN is far
    more dependable, if you have the luxury of highly-secure webserver directories.
    Exposing a connection string is like hardcoding a password.)

    Have you tried to connect to those SQL tables via ASP directly?(For the purpose
    of testing accessability from your webserver, you may want to test out simply
    connecting to the SQL Server.)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center