Click here to Skip to main content
15,901,122 members

Comments by Jennifer McCartthy (Top 5 by date)

Jennifer McCartthy 6-Dec-11 14:39pm View    
Hi Reiss,

Thank you again for your help, I greatly apprreciate it.
the changes you've made have helped me out but I'm now getting a rather contradictory couple of message boxes.

In the btnSaveDealSheet_Click event the connection state message box happily tells me the connection state is now open, but after trying to execute the Insert command the catch block throws me an error saying that the it cannot execute the command as the connection state is closed.

I'm at a bit of a loss on this one to be honest. Any suggestions...?

Thanks again for your help, I really do appreciate

Kind Regards
Jen
Jennifer McCartthy 6-Dec-11 6:14am View    
I'm not getting any errors at all. Just my message boxes telling me the connection state is closed.
Jennifer McCartthy 6-Dec-11 6:14am View    
Hi Reiss,

Thank you for your help.

Initially I wrote the app with a SQLConnection only to find that it is not compatible with SQLServer 2000 when using VS2010. I would love more than anything to use a SQL connection.

Thanks again for your help, its very much appreciated.

Kind Regards
Jen
Jennifer McCartthy 29-Aug-11 12:07pm View    
Afternoon, thank you for your reply.
we are using Access 2002. We are in a terminal services environment so they are all the same version. I haven't tried to reinstall office as the users are sharing the same instance of access and yet this problem is only happening for two users.
Jennifer McCartthy 26-Aug-11 8:51am View    
Your answer
thank you for your reply.

Yes, after the rs.open line it tells me "ERROR #3704 Operation is not allowed when the object is closed"

The parameters for rS.open are

rs.Open strSQL, dbRDDTCnn, adOpenDynamic, adLockOptimistic
strSQL is a simple SQL statement, and dbRDDTcnn is my connection object that tests to open.

Thanks again