ADODB Error on VI that hes worked for weeks without issue.

[Daddy-O]

We are about to go live testing on Monday with some LabVIEW code that has been working for weeks. I have made no changes, other than cosmetic in that time now I get this error. Other programs of mine for similar products use exactly the same database VIs, so I tried them. Also giving me this error. I may get fired of I can't fix this tomorrow. 

About to cry.

Chris.

[Yddet]

Hello,

I may not be able to help you but you really should give more information.

What are you trying to achieve, When/Where the error is generated, post your code. Did you modify the VIs of the database?

Write a list of all the changes you made, even small things. Every detail can be important.

     Did you deleted files from the system ?

     Did you update a software / driver /... ?

     If you changed a control, maybe the data type is different.

     If you modified a cluster, you may have changed the order of the controls inside (right click, reorder controls in cluster)

Do you still have a copy of the working version ? 

Yddet

[LLindenbauer]

ADODB errors are connected to database queries. I did a quick internet search for "800A0BCD ADODB" and it seems Your problem may not be LabVIEW-related at all, but may come from changes with the database You are using.

However, it's impossible to tell from what little information was given

[billko]

Firing the one person that may be able to fix the issue seems like a stupid thing to do, IMO.  Maybe when they realize what they've done, you can come back... for a substantial increase in pay.  😉

[Daddy-O]

I am pointing toward the database thing as well. I will work with the IT guy directly this morning. I would post my code but it is a state machine with 22 different states and  lots of DAQ hardware. I will follow up with a solution.

[Daddy-O · Accepted solution]

It turns out that the string our IT guy was providing me had an extra semicolon. I was right in the middle of this fairly long string. It was present in every dummy WO he provided me. 

I told him he owes me a beer for the 1/2 day I spun my wheels on this.

[billko]

---

@Daddy-O wrote:

It turns out that the string our IT guy was providing me had an extra semicolon. I was right in the middle of this fairly long string. It was present in every dummy WO he provided me. 

I told him he owes me a beer for the 1/2 day I spun my wheels on this.

---

I'm SO RELIEVED that you were able to figure out what was wrong!