Re: Access 2003 converts mdb when opened by VB app

From: Douglas J. Steele (NOSPAM_djsteele_at_NOSPAM_canada.com)
Date: 08/22/04 

Date: Sun, 22 Aug 2004 15:59:17 -0400

How are you opening it from VB? Are you just using DAO or ADO to get at the
data, or are you using Automation? If you're using Automation, how are you
doing it: with Early Binding (i.e.: you've set a reference to Access), or
Late Binding (i.e.: you haven't set a reference to Access, but are using
CreateObject("Access.Application")?

Unless you're using Automation, I can't see any way that the MDB would get
converted. And, to be honest, I find it hard to understand how converting
would cause the primary key to be lost, much less data fields. 

-- 
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"Doc Dunning" <docdunning@nowhere.net> wrote in message
news:cgamj6$lc2$1@hercules.btinternet.com...
> I wrote a standalone VB6 app a few years ago that maintains a .mdb
database.
> One of my users has reported today that its suddenly gone wrong, and is
> reporting missing indexes, fields etc.  He has Access 2003 installed, but
> that's been true for a while.
>
> Looking into it a bit more, what appears to happen is that when the VB app
> opens the database, the Access dlls are converting the mdb automatically
to
> the new format.  We see the dialog on screen to say that the db must be
> converted.  In the process it loses the primary key, and one other field
as
> well, which then makes it incompatible with the VB app.
>
> And ... he has just installed XP SP2, which makes me wonder if its
something
> to do with that ...
>
> Any ideas as to what might be causing this?
>
>
>

Relevant Pages

  • Re: Access 2003 converts mdb when opened by VB app
    ... Thanks for the reply, Doug. ... Are you just using DAO or ADO to get at ... If you're using Automation, how are you ... And, to be honest, I find it hard to understand how converting ...
    (microsoft.public.access.conversion)
  • Re: vb.net v. vsto
    ... Office automation is just to automate the office app through ... VSTO is not the development product, it's just extention for VS to work ... VSTO is an add-in to VS; ...
    (microsoft.public.dotnet.general)
  • Re: Cant "Quick View" second instance of System.Diagnostics.Process object
    ... Using Word automation you can access the opened documents and do what you will with them. ... You can do this by opening the project references dialog in VS.NET, ... Now, when you close your app, Word is closed too. ... >>> My problem is that I need to kill each instance individually, ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: vb.net v. vsto
    ... Office automation is just to automate the office app through its COM object ... VSTO is not the development product, it's just extention for VS to work ... VSTO is an add-in to VS; ...
    (microsoft.public.dotnet.general)
  • Strange behaviour at Application startup
    ... The app is built as an automation server to be controlled by an automation ... The app also uses OLE-DragAndDrop. ... disappear. ... With WinDbg I could localize the crash in the function ...
    (microsoft.public.win32.programmer.ole)