Re: How to add the security back to the normal database?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi Peter,

Have you ever considered, as one of PSS remits, to report to the Dev Team that
converting mdw's is a standard feature of the Conversion Menu, and you say has
bugs?

Bugs are for reporting and fixing, aren't they?

An article notifying a bug, is not a bug fix is it? This bug has been around
for enough time for someone to actually do something.

Background:
It is known that converting mdw's is mentioned as "dicey" by the SecFAQ. It
seems to actually work however, unless one is converting from A2.0 mda's where
it's fatal.

Since the article suggests the bug is known, why couldn't anyone at MS get off
their FA to fix it?

The other part of the background, is that re-creating mdw's anew is often
impossible, for a variety of historic reasons related to the complexity of ULS
(or slackness of programmers documenting PID's/WID's), and there is NO
technical reason why the purported "convert mdw files" is not supported.

(except that MS couldn't seem to be bothered fixing it)

Thankyou. I feel much better now!
(I personally have all my PID's, but it's still a major to re-create an mdw.
And I don't know whether those error messages matter, because in trying the
resulting converted mdw it seems to work. /would be better if it just
Fell-Over)
Regards,
Chris

"Peter Yang [MSFT]" <petery@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:TxA45zD6GHA.4348@xxxxxxxxxxxxxxxxxxxxxxxx
Hello Raghuram,

I fully agree with Joan's comments. Using shortcut might be the most
efficient method to manage different mdbs in different workgroup unless you
only have one Access database to run.

Usually it is not suggested that yu convert 97 version of mdw by using
Convert Database utility since there is some know issues, and you may want
to refer to the following article for more details:

824258 You receive error messages when you convert the workgroup
information (.mdw) file in Access 2003
http://support.microsoft.com/default.aspx?scid=kb;EN-US;824258

If you have any further questions or concerns, please feel free to let's
know. Thank you!

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support


=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================




.

Relevant Pages

  • Re: ULS Flaw?
    ... IF you convert a 97 mdw to later mdw it apparently works fine. ... over quick-smart on converting to a later version. ... I don't think that particular bug was known when they wrote the SecFAQ, ...
    (microsoft.public.access.security)
  • Re: ULS Flaw?
    ... IF you convert a 97 mdw to later mdw it apparently works fine. ... over quick-smart on converting to a later version. ... I don't think that particular bug was known when they wrote the SecFAQ, ...
    (microsoft.public.access.security)
  • Re: 2.6.28-rt on PowerPC
    ... BUG: sleeping function called from invalid context at kernel/rtmutex.c:683 ... This is trivially solved by converting arch/powerpc/sysdev/ipic.c ... back to spinlocks. ...
    (Linux-Kernel)
  • 2.6.28-rt on PowerPC
    ... BUG: sleeping function called from invalid context at kernel/rtmutex.c:683 ... Call Trace: ... This is trivially solved by converting arch/powerpc/sysdev/ipic.c ...
    (Linux-Kernel)
  • Re: Lebans PDF converter
    ... When I use the function in an Access file locally on my PC everthing is all ... The created PDF is the same as the original Report in my Access ... I tried to debug the code used by the function to convert an Access report. ... Could it be a printer property if the converting function is using some ...
    (microsoft.public.access.reports)