R
Rick Vooys
We have a large Access Application. The frontend is Access 97, and uses a SQL
Server 2005 Backend. We use ODBC to link the two.
All forms are working well, but on our "main" form, the Order Processing
form we are encountering some strange issues.
With no ryhme or reason, as the user enters items and does some of our more
complicated processes, during a refresh/requery the form "breaks". When I say
break, the underlying form recordset, the combo boxes "lose" it's data. I
have been trying to streamline the refresh/requeries but since we need to
keep the data updated with the SQL Server backend (it's not as quick to
update data, we get many Data Has Been Changed Warnings with the user and
code both working on the same data) I have littered the code with these lines?
I guess I am looking for any help. It seems to me like a memory issue, it
just gets too much going on and breaks. So I am trying to streamline the
code, but has anybody experienced this before? Any ideas? Any suggestions?
Thanks ahead of time.
Server 2005 Backend. We use ODBC to link the two.
All forms are working well, but on our "main" form, the Order Processing
form we are encountering some strange issues.
With no ryhme or reason, as the user enters items and does some of our more
complicated processes, during a refresh/requery the form "breaks". When I say
break, the underlying form recordset, the combo boxes "lose" it's data. I
have been trying to streamline the refresh/requeries but since we need to
keep the data updated with the SQL Server backend (it's not as quick to
update data, we get many Data Has Been Changed Warnings with the user and
code both working on the same data) I have littered the code with these lines?
I guess I am looking for any help. It seems to me like a memory issue, it
just gets too much going on and breaks. So I am trying to streamline the
code, but has anybody experienced this before? Any ideas? Any suggestions?
Thanks ahead of time.