<div>
mickeyshelley1,<br />
<br />
&quot;connecting to the server via a wireless Internet connection linking the database directly to the server.&quot;<br />
Well,... If you are using a wireless network form your laptop, &nbsp;you are not connected &quot;directly&quot; to anything.<br />
;-) <br />
<br />
At my company we/I tried running an Access Database over a wireless network, and as peter57r states, it was nothing but trouble, aggravation, frustration, ...ect. <br />
Not to mention the security concerns my company had about the wireless network being hacked.<br />
<br />
JeffCoachman
</div>


<div>
I too have had one client who insisted on running their Access application over a wireless network. It'd work fine for a couple of days, then corruption would hit. They finally moved to a wired connection and the issues went away. A wireless network, by it's nature, is not suitable for a fully bound application; the connection drops and remakes, and database connections don't like that.<br />
<br />
As pete said, use replication, or move the application to an unbound setup with a true server backend. You can then move most of the processing to the server (i.e. Stored Procs, Views, etc) at which point you're only passing a small text stream across the wireless. This tends to be much more robust, both in terms of performance and data integrity.
</div>


<div>
Thank you for the insightful commentary; the replication solution seems interesting, in this process how are the changed records managed? Is the complete record replaced for the more current record, or are only the changes made to the record appended to the original?<br />
<br />
mickey<br />

</div>


<div>
The information provided here was the best solution for my dilemma at present, in that it provides the functionality needed in absence of real-time solution. It also nudged me toward re-thinking the remote access issue in regards to Microsoft Access, as I hadnt considered the data connectivity problems. <br />
<br />
I would however be interested in commentary on MsAccess and terminal services (Remote Desktop)<br />
<br />
Mickey <br />

</div>


<div>
<div class="content wysiwyg-content">
Greetings:<br />
<br />
I am researching, what on the surface seems quite complicated and is difficult to clearly articulate but here it goes. <br />
<br />
I have an MsAccess2000 database that resides on a laptop. When I connect to the server I have programmed a command button to run an append query that in turn moves the data to a table on the server. This limits me to only adding new records. What I would like to do it to be able to add additional information to say a memo field in a record and then when I append back to the server only the records that have been edited will be changed leaving the original data intact but adding the additional information. &nbsp;<br />
<br />
Another consideration: If I add this database to another laptop, where another user will be adding information likewise, and two users by chance update the same record, would this pose a problem that could not be managed?<br />
<br />
I am looking into a second solution to the problem that is connecting to the server via a wireless Internet connection linking the database directly to the server. Is this practical? If what method? VPN?<br />

</div>
</div>


Greetings:

I am researching, what on the surface seems quite complicated and is difficult to clearly articulate but here it goes. 

I have an MsAccess2000 database that resides on a laptop. When I connect to the server I have programmed a command button to run an append query that in turn moves the data to a table on the server. This limits me to only adding new records. What I would like to do it to be able to add additional information to say a memo field in a record and then when I append back to the server only the records that have been edited will be changed leaving the original data intact but adding the additional information.  

Another consideration: If I add this database to another laptop, where another user will be adding information likewise, and two users by chance update the same record, would this pose a problem that could not be managed?

I am looking into a second solution to the problem that is connecting to the server via a wireless Internet connection linking the database directly to the server. Is this practical? If what method? VPN?


Appending Updated records VS Wireless Connection

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.

Microsoft Access

SQL (Structured Query Language) is designed to be used in conjunction with relational database products as of a means of working with sets of data. SQL consists of data definition, data manipulation, and procedural elements. Its scope includes data insert, query, update and delete, schema creation and modification, and data access control.