&Relationships Bug - workaround

ACCESS 2000

Just a quick note to leave for future developers.
This problem has been well documented in previous posts, but this little
trick may help future poor souls.

The error is when you try to import a database. I have learned that it is
possible to cure corruption of databases by creating a new mdb, and
importing all the objects from the misbehaving mdb into it.

However, a problem can occur when doing the import process, the current
object name being imported, gets "stuck" at an object called &Relationships.

It hangs , and when you 'break', you find that no forms have been imported,
and you cannot import any forms. If you have just done a days work, and you
find none of your forms is accessible, its a bit disheartening to say the
least.

In a desparate attempt not to have to re-work an extra day, I went back to
the original (corrupt) mdb. I opened each form in design view, and saved it
again under another name. I then found, that I could import the re-saved
forms, without the error occurring.

For what its worth, after 6 years of access development, this is the last
major project I am going to do in Access. I have had so many stupid
corruptions, slow operations, bugs, workarounds, that I am investigating
either VB.net or Delphi as my development environment. I have already gone
exclusively to MS-SQL as a back end, that cured many of the miseries
associated with using mdb's as data repositories. Despite some comments to
the contrary I have read, ADODB, in conjunction with Stored procedures has
ben an inherently reliable and speedy solution for me. I am not here to
justify my opinion or defend my point of view, but if anyone else finds
themselves in the same boat, just know you are not alone!

Thank you for the information. Could part of the problem have been
associated with this?

http://support.microsoft.com/kb/304548/


--
Wayne Morgan
MS Access MVP


"Ray Watson" <rwatson@oztell.com> wrote in message
news:dfnukh$1ip$1@nnrp.waia.asn.au...[color=blue]
> ACCESS 2000
>
> Just a quick note to leave for future developers.
> This problem has been well documented in previous posts, but this little
> trick may help future poor souls.
>
> The error is when you try to import a database. I have learned that it is
> possible to cure corruption of databases by creating a new mdb, and
> importing all the objects from the misbehaving mdb into it.
>
> However, a problem can occur when doing the import process, the current
> object name being imported, gets "stuck" at an object called
> &Relationships.
>
> It hangs , and when you 'break', you find that no forms have been
> imported,
> and you cannot import any forms. If you have just done a days work, and
> you
> find none of your forms is accessible, its a bit disheartening to say the
> least.
>
> In a desparate attempt not to have to re-work an extra day, I went back to
> the original (corrupt) mdb. I opened each form in design view, and saved
> it
> again under another name. I then found, that I could import the re-saved
> forms, without the error occurring.
>
> For what its worth, after 6 years of access development, this is the last
> major project I am going to do in Access. I have had so many stupid
> corruptions, slow operations, bugs, workarounds, that I am investigating
> either VB.net or Delphi as my development environment. I have already gone
> exclusively to MS-SQL as a back end, that cured many of the miseries
> associated with using mdb's as data repositories. Despite some comments to
> the contrary I have read, ADODB, in conjunction with Stored procedures has
> ben an inherently reliable and speedy solution for me. I am not here to
> justify my opinion or defend my point of view, but if anyone else finds
> themselves in the same boat, just know you are not alone!
>
>
>[/color]