TestStand and MS Jet Engine Conflict

[Grasshopper]

I have a MSVC++ 6.0 project interfacing with TestStand 2.0.1. I have an object that performs database operations on an Excel file using ODBC. What I have found is that I can perform database operations and then load a sequence without a problem, but if I try to perform another database operation after the sequence file load, I get a database error. If I move all the database operations to before loading a sequence then I don't have a problem if I use ReleaseSequenceFile(). Any ideas? Thanks.

[Scott_Richardson]

Grasshopper -
No ideas. TestStand loads and runs a sequence files when you log in to the sequence editor. What application are you using, Sequence Editor or OI? When you say that the problem only occurs after you load a file, did you successfully login? What was the error that the database call returned?

[Grasshopper]

Scott,
I'm using the Sequence Editor. What does OI stand for anyway? I did successfully login. The error is that the database engine believes it can't find a table, but if a sequence wasn't loaded before the call, it can find the table. Here's the flow currently:
1. Start the App
2. Create the TestStand Engine
3. Login to TestStand
4. Perform a database call
5. Use results for other stuff ( non-TestStand related )
6. Load a sequence
7. Sequence loaded
8. Repeat 4 ( fails )
It's the same exact call except I'm looking for a different value in one of the fields. The error is that the table can't be found. It doesn't make any sense how to the two are related. Thanks.
-G-

[Grasshopper]

Scott,
This may help. If a CFileDialog is created ( not even displayed, just created ) or a DisplayOpenFileDialog is created then the next ODBC call will fail. Hopefully, that will provided a starting point. Thanks.
-G-

[Grasshopper]

Scott,
I got it. It didn't have anything to do with the Jet engine. Basically, when the open file dialog pops up, if the path is changed to find a sequence then the current working directory is modified. The paths I provided to the database object are all relative and thus it really couldn't find the table. Thanks for the help.
-G-

[Scott_Richardson]

G -
I was stumped. Thanks for letting me know the cause. Sorry for the "OI", it stands for Operator Interface.