title: DAO vs ADO in HTA over wireless
body: <p>I've written a small (8-10 laptops) point-of-sale system running over a wireless network, as an HTA that reads from/writes to an Access MDB located on a network share.<br/>
  I need to use ADO - GetString and the user roster are not available with DAO.<br/>
  I also need to use DAO - the MDB cannot be compacted with ADO.</p>
  
  <p>I know that:<br/>
  1) If the database backend is not an Access MDB, I should use ADO.<br/>
  2) If the backend is an MDB, but I want to upgrade to SQL Server at some point, I should use ADO.<br/>
  3) Within an Access application, or any other VBA/VB application, I should use DAO, as ADO must go through a translation layer of the Jet OLE DB Provider, while DAO is more direct.<br/>
  4) VBScript/JScript allows me to use either DAO or ADO.</p>
  
  <p>The two-part question is as follows:<br/>
  1) In this software environment (HTA/scripting), is it better to use ADO rather than DAO?<br/>
  2) Does ADO offer any benefits because the HTA is reading/writing over a wireless network?</p>