Re: Access 2000 to Access 2003
- From: "Allen Browne" <AllenBrowne@xxxxxxxxxxxxxx>
- Date: Sat, 16 Jul 2005 13:24:44 +0800
Yes, Rachel, as Ronald says, the best solution is to uncheck the reference
marked 'MISSING' under:
Tools | References
from a code window.
Functions such as Format() and Left() are supplied by the VBA libaray, which
is not the missing one. However, once a reference is missing *nothing* works
reliably. Remove the bad reference, and the others will work again, though
your project will not compile if it contains code that tries to call the
removed reference.
That's why the suggestion was to remove that code as well, and use the API
calls, so you won't have this problem in the future.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Ronald Roberts" <rwr@xxxxxxxxxx> wrote in message
news:uu7Y5UciFHA.3448@xxxxxxxxxxxxxxxxxxxxxxx
> You can correct this by opening a module and from the menu select
> Tools/Reference. Look for MISSING REFERENCE. I haven't had this
> problem for a while but I think you need to uncheck it.
> If nothing else, do the opposite of what it says.
>
> Rachel wrote:
>
>> Any idea how to solve the formatting problem or other scripting problems?
>>
>> Forinstance, the Format function does not work and the Right and Mid
>> functions also do not work. I am not writing super in-depth coding, so
>> it is frustrating that I cannot do the simple stuff.
>>
>> "Allen Browne" wrote:
>>
>>
>>>Hi Rachel
>>>
>>>The MS ActiveX controls such as common dialog and calendar are very much
>>>prone to breaking and versioning issues, and - as you found - once a
>>>reference is broken nothing works.
>>>
>>>The best solution is to avoid these controls. For example:
>>> http://www.mvps.org/access/api/index.html
>>>contains many of the API calls you need for the File Open dialog, system
>>>fonts, the color dialog, and so on. By using the API calls instead of the
>>>ActiveX controls, there is no extra reference to break.
>>>
>>>This way you can get by with as few as 3 references, and these normally
>>>don't break when switching version. More info on that:
>>> http://allenbrowne.com/ser-38.html
>>>
>>>
>>>"Rachel" <Rachel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>>>news:2D0F3996-6BE3-4D00-A629-4A3F4EAD8F65@xxxxxxxxxxxxxxxx
>>>
>>>>When I opened my Access 2000 database in Access 2003 I the reference to
>>>>the
>>>>Common dialog control is missing and the code that I wrote has problems
>>>>now.
>>>>Forinstance the Format statement is not recognized. It states that it
>>>>needs
>>>>the proper library to work. Ok, there must be a reference that I need
>>>>to
>>>>check. I thought that it was attempting to convert the vb to vb.net and
>>>>I
>>>>attempted to add the System.convert in the code by using the statement
>>>>Imports System.Convert and it is also not recognized. Any help is
>>>>appreciated. I know VB 6.0 as well as VB.net and some VBA so please
>>>>help me.
.
- References:
- Access 2000 to Access 2003
- From: Rachel
- Re: Access 2000 to Access 2003
- From: Allen Browne
- Re: Access 2000 to Access 2003
- From: Rachel
- Re: Access 2000 to Access 2003
- From: Ronald Roberts
- Access 2000 to Access 2003
- Prev by Date: Re: Access 2000 to Access 2003
- Next by Date: Re: Variables being reset after conversion from 97 to 2000
- Previous by thread: Re: Access 2000 to Access 2003
- Index(es):
Relevant Pages
|
