G
Guest
I quote another user on this forum, as I have not seen this as an own question.
"I have another problem with access 2003 with sp3 adp poject. If you
have a table with a bit column and default value 0 before sp3 access
insert correctly false, after sp3 access insert true. This is only one
problem, with sp3 i discover a lot of problem, im very scared !!!"
We have a field in our CustomersTable on the SQL that we call, say
"CustomerLocked".
This is a bit value that defaults to 0.
When an Agent opens a customer through the ADP Access file, a Stored
Procedure runs on the SQL. That procedure selects an appropriate cutomer,
sets "CustomerLocked" to 1 and then sends "Select * from Customer where ID =
xxx" as the rowsource to Access.
When the Agent is done with the Customer a set of VBA commands is run and
one of them is:
Me.CustomerLocked.Value = False
But for some reason this does not affect the customer in the database.
But even more strange is that it sometimes actually do work.
We are baffled by this, and cannot see a possible solution to this!
What we do now is run a job that resets the "CustomerLocked" to 0 every night.
But our Agents can only contact the Customers once per day, until this is
resolved.
Its urgent!
Ideas?
Note: This is not our only problem so far...
I have more posts written.
"I have another problem with access 2003 with sp3 adp poject. If you
have a table with a bit column and default value 0 before sp3 access
insert correctly false, after sp3 access insert true. This is only one
problem, with sp3 i discover a lot of problem, im very scared !!!"
We have a field in our CustomersTable on the SQL that we call, say
"CustomerLocked".
This is a bit value that defaults to 0.
When an Agent opens a customer through the ADP Access file, a Stored
Procedure runs on the SQL. That procedure selects an appropriate cutomer,
sets "CustomerLocked" to 1 and then sends "Select * from Customer where ID =
xxx" as the rowsource to Access.
When the Agent is done with the Customer a set of VBA commands is run and
one of them is:
Me.CustomerLocked.Value = False
But for some reason this does not affect the customer in the database.
But even more strange is that it sometimes actually do work.
We are baffled by this, and cannot see a possible solution to this!
What we do now is run a job that resets the "CustomerLocked" to 0 every night.
But our Agents can only contact the Customers once per day, until this is
resolved.
Its urgent!
Ideas?
Note: This is not our only problem so far...
I have more posts written.