Yes, the Application is split
2 frontend and 1 database
when the 2 are updated simultaneously, that is running the update sql code through VBA, the one hosting the backend will go through, while the other will complain like "error running sql, or the other user has opened the program in Admin mode" and then freeze up
Here is the SQL statement:
(On Error Resume Next
Dim SQL As String
Dim SQL2 As String
SQL = "UPDATE tblOutbound INNER JOIN tblItem ON tblOutbound.ItemID = tblItem.ItemID SET tblItem.QtyAvail = [tblItem].[QtyAvail]-[tblOutbound].[QtyOut], tblItem.UnitSale = [tblOutbound].[ExtendedPrice], tblOutbound.ClientID = [Forms]![frmPoS]![cboClient] WHERE (((tblOutbound.InvoiceNo)=[forms]![frmPoS]![InvoiceNo]));"
SQL2 = "UPDATE tblClient INNER JOIN tblOutbound ON tblClient.ClientID = tblOutbound.ClientID SET tblClient.ClientAcc = [tblClient].[ClientAcc]+[tblOutbound].[AmountRecorded] WHERE (((tblOutbound.InvoiceNo)=[forms]![frmPoS]![OutboundInv]));"
DoCmd.SetWarnings False
DoCmd.RefreshRecord
DoCmd.RunSQL SQL
DoCmd.RunSQL SQL2
DoCmd.SetWarnings True)