Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
VFP Front-end, SQL Server back-end...modem
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Client/serveur
Divers
Thread ID:
00503981
Message ID:
00503983
Vues:
20
Hi Kevin,

Yep this makes sense.

A few random ramblings:
  • Think about having tables that don't change very often (post code lookups etc) as local tables
  • if you need true off-line capabilities and if the laptop's got the grunt, consider using MSDE and replication so that all you need to do is point the DSN at the local SQL server engine and any changes are made the next time the user's logged onto the network
  • Make sure that if you're accessing the (central) server over the internet that there are no firewalls blocking port 1433 (the SQL server TCP/IP port)
  • If you're dialing straight into the network that hosts the central server, then you shouldn't have to make any changes to the code (except perhaps for considering the local tables issue in the first point above)

    Cheers,

    Andrew

    >The other day, someone asked me a question that partly stumped me.
    >
    >Basically, suppose someone had a front-end written in VFP that accessed SQL Server tables. The front-end was running on a client's laptop, the SQL Server database was running at a corporate location, and the client had nothing more than an ISP dial-up at less than 56 kbs.
    >
    >Most of the VFP->SQL Server setups I've seen have still involved LANs or Citrix, so I basically have two questions:
    >
    >1) From a syntax standpoint, what would you need in addition to the standard SQLCONNECT/SQLEXEC commands to an ODBC source? (As far as connection strings, etc.)
    >
    >2) Does this type of setup (someone accessing SQL Server tables from a VFP front-end with a dial-up connection of 56 kbs or less) even make sense?
    >
    >Kevin


    If we were to introduce Visual FoxBase+, would we be able to work from the dotNet Prompt?


    From Top 22 Developer Responses to defects in Software
    2. "It’s not a bug, it’s a feature."
    1. "I thought I fixed that."


    All my FoxTalk and other articles are available on my web site.


    Unless specifically identified otherwise, anthing posted here is purely my opinion and may or may not reflect the policies or practices of Microsoft.
  • Précédent
    Répondre
    Fil
    Voir

    Click here to load this message in the networking platform