J
JK
Well, since all of you “geeks†(just kidding) have been arguing about stuff
way over my head, something strange happened. All by itself the ADO reference
reappeared.
This is bothering me – I seem to be experiencing issues that only Vista
users should be experiencing. I don’t have Vista nor do any of my application
users.
So not only did I have the problem with the ADO reference but, I also
somehow registered and selected the Microsoft Office 12.0 Object Library.
From what I’m told that reference is for Vista machines as well. My computer
is confused, it thinks it’s a Vista machine but it’s NOT! I don’t recall
doing it but I suppose I could have installed the Vista trial version way
back when – which is probably causing these problems.
Someone in this thread mentioned linked ODBC tables. I actually have a whole
bunch of them; they’re linked to J.D. Edwards. A factor? I don’t know…
Like I said, this is way over my head but it was very interesting to hear
what you guys had to say on the subject. I will try the “ADOX.IsBrokenâ€
example today. Although my app. seems to be working now, who’s to say these
reference issues won’t reappear.
JK
way over my head, something strange happened. All by itself the ADO reference
reappeared.
This is bothering me – I seem to be experiencing issues that only Vista
users should be experiencing. I don’t have Vista nor do any of my application
users.
So not only did I have the problem with the ADO reference but, I also
somehow registered and selected the Microsoft Office 12.0 Object Library.
From what I’m told that reference is for Vista machines as well. My computer
is confused, it thinks it’s a Vista machine but it’s NOT! I don’t recall
doing it but I suppose I could have installed the Vista trial version way
back when – which is probably causing these problems.
Someone in this thread mentioned linked ODBC tables. I actually have a whole
bunch of them; they’re linked to J.D. Edwards. A factor? I don’t know…
Like I said, this is way over my head but it was very interesting to hear
what you guys had to say on the subject. I will try the “ADOX.IsBrokenâ€
example today. Although my app. seems to be working now, who’s to say these
reference issues won’t reappear.
JK