From: NoSpam@spam.com   
      
   "Steven"  wrote in message   
   news:m96dnd4oMJZNh3rcRVn-tg@rogers.com...   
   > hi all   
   >   
   > i'm primarily a ASP web developer, so i'm not sure if i can do this or   
   not.   
   > i want to allow client's on my site to run a local version of the site off   
   > their laptop. i want to give the user an option on the site that grabs all   
   > the ASP pages, extracts just their records for MS SQL and exports to MS   
   > Access, then packs into a zip file for download. no problem with any of   
   the   
   > steps so far. what should happend next is the user runs my app which:   
   >   
   > a. checks to see if PWS is installed on the machine and if so, is there a   
   > domain set up to point to my pages. if not, install PWS and add the   
   domain.   
   > b. copy my files to "c:\local_web_site"   
   > c. adds a favourites pointing to the PWS server in IE   
   > d. starts PWS, opens IE and goes to the directory.   
   >   
   > is this possible? the big question is the business of sniffing for a PWS,   
   > installing if necessary, and adding the domain info.   
   >   
   > tks   
   >   
      
   Sounds a bit overkill to me, with trip ups   
   Restarts, configuration,etc..   
   A user not familiar with PWS   
   A large help desk - comes to mind.   
      
   I think a better option would be to   
   provide a download to install an AX.   
   (If Clients use only IE then AX docs sound good to me)   
      
   Also added to the favs and optionaly to the start menu:   
   When run (or browsed to) an option loads to go live   
   ,download, or use offline   
   (page link option or intergrated into IE's Menu's)   
      
   (Download as data or database which ever you prefer)   
   Create and/or store the database locally.   
   Options then to update it.   
   (either viewed in IE (DLL,EXE) or in outside forms IE (EXE) -   
    like the way Windows update functions)   
      
   Admittedly it means you would need to re-write/convert   
   your server side scripts and client HTML/Scripts,   
   in to a VB compiled dll or exe.   
      
   Still, it would give you online calls to your server and be able to manage   
   the data locally all from within IE.   
   You would have the freedom when coding of knowing that your Server pages are   
   always clients online and your AX is local with options to go online.   
      
   To simplifiy things a separate web application on your side to provide the   
   download and manage the update capabillities.   
      
   Once tested a few links and its live with little change/upset to the stuff   
   you already have.   
      
   I am sure there are be plenty of people in here that can/will help with the   
   VB side of things if  :   
   a) you decide to tackle it   
   b) you get stuck .   
      
   Geoff   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)