Especially if it does not need too wide of a bandwidth. Does it need a static IP? If it can work that way, then it is only about what is already available and whatever it will cost to change it. Which I need to check on Monday. Hi, I thought I should at least inform you that our company finally decided to go the way you suggested, that is using Terminal Server via internet. I like to thank you for all the insights and the patience that you have given me.
Especially, after I reread my questions and answers, they do sound rather like dumb questions. I am sorry for that. I also apologize for the late reply, as I want to make sure the final decision of the company first, before I write this. Once, again thank you so much for your kind help and patience. The next time if you pass through Indonesia, by any chance, please let me know, I will try my best to repay the favour, :. Tony Toews [MVP]. Nothing to apologize for. All questions sounds dumb after you get the answer.
Dear David, I just want to let you know that our company finally adopts your suggestion, that is to use terminal server. I like to thank you personally for all your suggestions and patience. I have reread my posts, and they do sound rather dumb, once I understand a bit more about terminal server and VPN.
Besides, I learnt everything about programming by selftaught, hence many parts are pretty spotty, for areas that I never learnt. I am a Chemical Engineer by training. Again, thank you so much for your patience and help. This is a reply after a long time, because I want to wait until my company makes the decision. The next time you pass through Indonesia, please let me know, and I would really like to take the opportunity to return the favour.
This discussion thread is closed Start new discussion. SQL Server - Access synchronization. Advice on an expanding Access project. Access Back-End Over the Internet? Multi-user, offline use for Access database. ASP access to Data on Remote devices. Mobile Development. Software Development. Remote Development and Debugging Tools. Nested class structure question. Those are just two methods of accomplishing automated Jet synchroniziation without needing to open your Access application.
JRO is really not the best way to manage Jet Replication. For one, it has only one function in it that DAO itself lacks, i. But if you're going to add a dependency to your app JRO requires a reference, or can be used via late binding , you might as well add a dependency on a truly useful library for controlling Jet Replication, and that's the TSI Synchronizer , created by Michael Kaplan, once the world's foremost expert on Jet Replication who has since moved onto internationalization as his area of concentration.
It gives you full programmatic control of almost all the replication functionality that Jet exposes, including scheduling synchs, initiating all kinds of synchronization, and the much-needed MoveReplica command the only legal way to move or rename a replica without breaking replication. Its purpose is to provide Jet-specific functionality to supplement what is supported in ADO itself. As I said above, it adds only one function that isn't already available in DAO i.
I can't help but think that Microsoft was being spiteful by creating a standalone library for Jet-specific functionality and then purposefully leaving out all the incredibly useful functions that they could have supported had they chosen to.
Now that I've disposed of the erroneous assertions in the answers offered above, here's my recomendation:. Because you have an append-only infrastructure, do what Remou has recommended and set up something to manually send the new records whereever they need to go. And he's right that you still have to deal with the PK issue, just as you would if you used Jet Replication.
But one caveat: if the add-only scenario changes in the future, you'll be hosed and have to start from scratch or write a whole lot of hairy code to manage deletes and updates this is not easy -- trust me, I've done it!
One advantage of just using Jet Replication even though it's most valuable for two-way synchronizations, i. You should read into Access Database Replication , as there is some information out there. But I think that in order for it to work correctly with your application, you will have to roll out a custom made solution using the methods and properties available for that end.
Use Jet and Replication Objects JRO if you require programmatic control over the exchange of data and design information among members of the replica set in Microsoft Access databases. For example, you can use JRO to write a procedure that automatically synchronizes a user's replica with the rest of the set when the user opens the database. To replicate a database programmatically, the database must be closed.
If your database was created with Microsoft Access 97 or earlier, you must use Data Access Objects DAO to programmatically replicate and synchronize it. You can create and maintain a replicated database in previous versions of Microsoft Access by using DAO methods and properties.
Use DAO if you require programmatic control over the exchange of data and design information among members of the replica set. For example, you can use DAO to write a procedure that automatically synchronizes a user's replica with the rest of the set when the user opens the database. Microsoft Jet provides these additional methods and properties for creating and maintaining partial replicas replicas that contain a subset of the records in a full replica :. You should definitely read the Synchronizing Data part of the documentation.
I used replication in a00 for years, until forced to upgrade to a07 when it went away. If not managed timely, or there are too many, users get frustrated and the data becomes unreliable. Replication did work well when our remote sites were not always connected to the internet. This allowed them to work with their data, and synchronize when they could.
At least twice daily. We install a separate database on the remote computers that managed the synchronization, so the user only had to click an icon on their desktop to evoke the synchronization.
This process worked quite well, as we had 30 of these "nodes" working around the country, managing their data and updating to the FTP servers. Privacy policy. Typically, a driver's InterruptService or InterruptMessageService routines ISRs must share access to driver data and hardware resources with other driver routines. Since ISRs execute in an interrupt context at an elevated IRQL, and since a system might have multiple processors, it is important to synchronize access to shared data and resources so that each routine can be guaranteed to temporarily have exclusive access to this shared information, without interruption.
The system supports this synchronization by executing the ISR within an interrupt critical section. The system guarantees this code executing within the critical section exclusive access to shared information, by raising the processor's IRQL to the interrupt synchronization IRQL and acquiring the interrupt spin lock before executing the code.
The system always enters the interrupt's critical section before executing its ISR. Create a Navigation form and set it as the default form to display on start. There are a few tasks that you should perform before you start to design your web database. Moreover, there are design differences between web databases and desktop databases that you should know about, especially if you are an experienced Access developer.
Determine the purpose of your database Have a clear plan so you can make good decisions when working out design details. Find and organize the information required You cannot use linked tables in a web database. Any data that you want to use that will not originate in the database must be imported before you publish.
If you line up your data before you start designing, you can avoid having to refit your design to accommodate unexpected data challenges. If you want to test your design in a browser while you design it not a bad idea , you have to publish it first. Plan your security You can take advantage of SharePoint security to control access to your web database.
Plan security early so you can build it into your design. Some database features that you can use in a desktop database are not available with Access Services.
However, there are new features that support many of the same scenarios as these desktop features. The following table lists the desktop-only features, and the new feature that helps support the same scenario.
Important: You can create many client objects in a web database, but you cannot use them in a browser. However, they are part of the web database and can be used in Access on the desktop. People can open the web database in Access, and then use the client objects.
This is an effective way to share a database, and also opens new opportunities for working together over the Web. SharePoint handles any concurrency issues.
When you have determined what your application must do, consider whether a database template would work. Database templates are pre-built applications that you can use as-is or modify to suit your particular needs. You can review the available templates on the New tab in Backstage view.
For more information about the templates that come with Access , see the article Select and use an Access template. The File tab opens Backstage view, a new part of the Access interface where you'll find commands that apply to an entire database, such as Publish to SharePoint. Review the proposed file name in the File Name box, and the path for the database file, listed just below. You can change the file name by typing in the File Name box. To change the path, click the folder icon next to the File Name box to browse for a location to put your database file.
Click Create. Your new web database opens and displays a new empty table. When you first create a blank web database, Access creates a new table and opens it in Datasheet view. You can use the commands on the Fields tab and the Table tab to add fields, indexes, validation rules, and data macros — a new feature that lets you change data based on events. On the Create tab, in the Tables group, click Table.
When you first create a table, it has one field: an AutoNumber ID field. You can add new fields to store the items of information required by the table subject.
For example, you might want to add a field that stores the date you begin tracking something. You can choose from a variety of preformatted fields and add them to your table by using the field gallery. Tip: To change the name of an existing field, double-click the field name. Formatting and properties determine how a field behaves, such as what kind of data it can store.
You can change these settings so that the field behaves the way that you want. Use the commands in the Formatting and Properties groups to change the settings. You can add a field that displays a value that is calculated from other data in the same table. Data from other tables cannot be used as the source for the calculated data.
Some expressions are not supported by calculated fields. Point to Calculated Field , and then click the data type that you want for the field. Use the Expression Builder to create the calculation for the field. Remember that you can only use other fields from the same table as data sources for the calculation.
You can use an expression to validate input for most fields. You can also use an expression to validate input for a table, which can be useful if you want to validate input for a field that does not support validation, or if you want to validate field input based on the value of other fields in the table.
For a more thorough explanation of validation, see the article Restrict data input by using a validation rule. You can also specify the message that is displayed when a validation rule prevents input, known as a validation message.
0コメント