You would just need to make a Jet or ADO connection to the other database, and then create a recordset that either updates or inserts your data.
How are you packaging the data that is going to be sent to the other database? Where is the other database? Is it on your LAN? If so, how many database instances will be sending data to the other database (just you, or 100 other users?) Also, will the receiving database be used for transactions in real time other than the ones you are sending? Will you use a DSN?
If you were using a form, for example, and sending a user's first and last names, identifying the record with a PK that was the same in both databases, your code would look something like:
Dim lPK As Long
Dim sLast As String
Dim sFirst As String
Dim cn As ADODB.Connection
Dim rs As ADODB.Recordset
Dim sSQL As String
lPK = Me.ID
sLast = Me.LastName
sFirst = Me.FirstName
sSQL = "UPDATE tblMyOtherDatabaseTable " & _
"SET [LastName] = '" & sLast & "', " & _
"[FirstName] = '" & sFirst & "' " & _
"WHERE ID = " & lPK
cn.Open "Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=\my_path\MyOtherDatabase.mdb;" & _
"User ID=userid;" & _
Set rs = New ADODB.Recordset
rs.Open sSQL, cn, adOpenDynamic, adLockOptimistic
'the act of opening the recordset using the connection object updates the database.
So something like this would work. You can also use a DSN and lose some of the connection string.
Did that help?
Look it up at: http://wrox.books24x7.com