G
Gail
I am developing an application using unbound forms to
enter, view and edit records in various tables. The save
routine is a function called from a stand-alone module.
Elements to build the connection string and criteria
filters are embedded on each form. The primary table is a
customer master, keyed to the unique customer number. The
customer items table is 1:Many where one customer number
can have multiple items. There is a unique key of the item
number used to reference this table. Tables are stored in
SQL 7.0 on an NT4.0 server, and I'm using Access 2000 on
an NT4.0 machine as the project front-end.
In a nutshell, I started having problems saving the items
table yesterday. The function processes and reports the
record is saved, but nothing is added to the table. So I
went back to the master form and tried to enter another
new customer (which was working fine through yesterday.)
Now, I am getting an error that multiple ole actions
caused an error and no work was done. The connection
string was changed from Provider=SQLOLEDB; to
Provider=SQLOLEDB.1;. All tables exist in the same SQL
database. It's almost as if the connection has become
corrupt or something. It does not appear that the
connection is closed at any point in the code. Record sets
are, but not the connection. Yet it is rebuilt every time
the function (or any function in the module) is called.
When this started, I was calling the items form from the
master form. In case that was causing the problem, I tried
working from the items form directly this morning with the
same result. I do check to see if the form calling the
next one needs to be saved before moving on to the next
form.
Any suggestions? I am rather new at this, and have gotten
most of my information from the book "Access 2002 Bible"
by Cary Prague and Michael Irwin. I found it fairly easy
to understand and follow. The code I'm using for the
unbound forms is taken directly from the book.
Gail
enter, view and edit records in various tables. The save
routine is a function called from a stand-alone module.
Elements to build the connection string and criteria
filters are embedded on each form. The primary table is a
customer master, keyed to the unique customer number. The
customer items table is 1:Many where one customer number
can have multiple items. There is a unique key of the item
number used to reference this table. Tables are stored in
SQL 7.0 on an NT4.0 server, and I'm using Access 2000 on
an NT4.0 machine as the project front-end.
In a nutshell, I started having problems saving the items
table yesterday. The function processes and reports the
record is saved, but nothing is added to the table. So I
went back to the master form and tried to enter another
new customer (which was working fine through yesterday.)
Now, I am getting an error that multiple ole actions
caused an error and no work was done. The connection
string was changed from Provider=SQLOLEDB; to
Provider=SQLOLEDB.1;. All tables exist in the same SQL
database. It's almost as if the connection has become
corrupt or something. It does not appear that the
connection is closed at any point in the code. Record sets
are, but not the connection. Yet it is rebuilt every time
the function (or any function in the module) is called.
When this started, I was calling the items form from the
master form. In case that was causing the problem, I tried
working from the items form directly this morning with the
same result. I do check to see if the form calling the
next one needs to be saved before moving on to the next
form.
Any suggestions? I am rather new at this, and have gotten
most of my information from the book "Access 2002 Bible"
by Cary Prague and Michael Irwin. I found it fairly easy
to understand and follow. The code I'm using for the
unbound forms is taken directly from the book.
Gail