Prev: Detecting Accde database
Next: Can't use recordset after splitting
From: Marshall Barton on 21 Jun 2010 22:47
Bob Darlington wrote:

>Thanks Marsh and Doug,
>I'll try that today.
>By the way Marsh, what is the go with having to select all objects
>individually?


If you select all modules, the bad one will be selected, but
the bad one will either not be there to deselect or you will
be unable to deselect it because of the same problem that
module has when you tried the other things. Then the import
will fail on the bad module.

If you know it is a bad module, then you can use select all
on other type of objects, just not module objects. If it a
form or report or a form/report module then avoid using
select all for the form or report objects.

--
Marsh
From: Bob Darlington on 21 Jun 2010 23:57
Thanks Marsh. That makes sense.

--
Bob Darlington
Brisbane
"Marshall Barton" <marshbarton(a)wowway.com> wrote in message
news:ld80261e8saej641ieq7g4e7j9n1v29qtv(a)4ax.com...
> Bob Darlington wrote:
>
>>Thanks Marsh and Doug,
>>I'll try that today.
>>By the way Marsh, what is the go with having to select all objects
>>individually?
>
>
> If you select all modules, the bad one will be selected, but
> the bad one will either not be there to deselect or you will
> be unable to deselect it because of the same problem that
> module has when you tried the other things. Then the import
> will fail on the bad module.
>
> If you know it is a bad module, then you can use select all
> on other type of objects, just not module objects. If it a
> form or report or a form/report module then avoid using
> select all for the form or report objects.
>
> --
> Marsh


First  |  Prev  | 
Pages: 1 2
Prev: Detecting Accde database
Next: Can't use recordset after splitting