J
JohnE
The company has this a complex Access db that has grown over the past 10
years and moved along with the different versions. It is now an A2003. It
is an A2003 front end with SQL2005 backend. The company is going to Office
2007 which will also include A2007. When running the app in A2007 the
ODBCDirect not supported notice is recvd. The correction for this is to move
to ADO. The app is not being converted to ACCDB or ACCDE. What have others
in the community done about this issue?
During the testing we were also getting the notice that required us to sign
into the SQL server on just about every form. This has been a thorn in our
sides and I am wondering if anyone else has had this problem and how was it
corrected?
In tackling the move to A2007, are there any "gotchas" that should be known?
I have looked over the article by Allen Browne and was wondering if others
moving to A2007 what problems have been encountered?
Thanks.
John
years and moved along with the different versions. It is now an A2003. It
is an A2003 front end with SQL2005 backend. The company is going to Office
2007 which will also include A2007. When running the app in A2007 the
ODBCDirect not supported notice is recvd. The correction for this is to move
to ADO. The app is not being converted to ACCDB or ACCDE. What have others
in the community done about this issue?
During the testing we were also getting the notice that required us to sign
into the SQL server on just about every form. This has been a thorn in our
sides and I am wondering if anyone else has had this problem and how was it
corrected?
In tackling the move to A2007, are there any "gotchas" that should be known?
I have looked over the article by Allen Browne and was wondering if others
moving to A2007 what problems have been encountered?
Thanks.
John