Because our test team works across a WAN, I have attempted a temporary workaround.
I have been working with the /Program Files/Compuware/TestPartner.mdb on my harddrive.
This was working well enough for me, but if I did work with someone else's scripts, there were issues related to mapped objects ... that I didn't have. I was scared to import the db onto my hd because I have seen kind of db transfer blow up too many times. Never the less, I was talked into importing the objects into my personal db.
It blew up. I have a script that types information into the Windows Run command line after accessing the Start button. It took 4-5 seconds for each character to come across from TP into the field!
To rid myself issues caused by my import, I began to delete objects by type.. one at a time and rerun the program to see if it helped. It did not.
Finally, I renamed the db and allowed TP to reconfigure itself. This seems to have helped with the aforementioned issue, however, there are issues now with scripts that used to run just fine. Object recognition is what I have seen so far.
My backup was not of the .mdb file, but in a .xml file of the original exported objects.
First question is -
Why did the export / import process corrupt my existing db?
Next, Why is my backup file / my backup objects now failing?
Also, How can I correct this mess?
Finally, How can I successfully import objects from another TP DB without corrupting my current DB?
I do not believe that a reinstall will help unless I import the scripts that I wrote via cut and paste into notepad and reassign the object maps.
There is something fishy about my .xml files.
This is very frustrating. I wrote a new script this morning that worked very well. Went into the remote db to just 'peek' at a script, and viola! my local scripts broke. They don't recognize javawindow(xy, z) anymore!
I am two centimeters from unistalling and reinstalling TP on my hard drive.
I did a db integrity check on my local db's, including the one I suspect to be corrupt. Nothing showed up.
The remote db admin will perform that check for me on their db, Friday night. Meanwhile... *twiddle*