J John Mar 25, 2008 #1 Hi Is it possible to compact and repair an external access 200 database via code? Thanks Regards
G Guest Mar 25, 2008 #2 Is it possible to compact and repair an external access 200 database via code? Click to expand... AFAIK, you can't via ADO.NET. But you can use classic ADO. http://support.microsoft.com/kb/230501
Is it possible to compact and repair an external access 200 database via code? Click to expand... AFAIK, you can't via ADO.NET. But you can use classic ADO. http://support.microsoft.com/kb/230501
G Guest Mar 25, 2008 #3 Ah, no. It takes JRO. Click to expand... Isn't JRO part of ADO? That's what the knowledge base article says. Ha Ha.
Ah, no. It takes JRO. Click to expand... Isn't JRO part of ADO? That's what the knowledge base article says. Ha Ha.
G Guest Mar 25, 2008 #4 Not in any build/deployment I've seen... but it's been awhile. Click to expand... BTW, I was just being sarcastic ;-)
Not in any build/deployment I've seen... but it's been awhile. Click to expand... BTW, I was just being sarcastic ;-)
C Cor Ligthert[MVP] Mar 26, 2008 #5 BTW, I was just being sarcastic ;-) Click to expand... I thought it was meant to help Bill. As is proven is everybody using forever the same ways to solve things (and tell about that). In my idea does another light on that helps to improve that. Cor
BTW, I was just being sarcastic ;-) Click to expand... I thought it was meant to help Bill. As is proven is everybody using forever the same ways to solve things (and tell about that). In my idea does another light on that helps to improve that. Cor
P Paul Clement Mar 26, 2008 #6 ¤ ¤ > Ah, no. It takes JRO. ¤ ¤ Isn't JRO part of ADO? ¤ Different library, actually an extension to ADO since it lacks the functionality - but they're both installed via MDAC. Paul ~~~~ Microsoft MVP (Visual Basic)
¤ ¤ > Ah, no. It takes JRO. ¤ ¤ Isn't JRO part of ADO? ¤ Different library, actually an extension to ADO since it lacks the functionality - but they're both installed via MDAC. Paul ~~~~ Microsoft MVP (Visual Basic)