prompts for format in runtime?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Knox - 30 Mar 2005 15:59 GMT

I had a runtime distributed program that was working fine. I made what I
thought was a minor upgrade to it, not even touching the affected part.

I have a report that in the query has a [Enter beginning date] and [Enter
end date]. That works fine and continues to work. The report has a field
that has =Format( <stuff>). The runtime version now prompts for Format
just like it prompts for [Enter beginning date].

It works fine in the development environment. It's as if I didn't include
the right vba utility or something, but I didn't change that. In fact, if I
copy the current MDB over the old one, it does the same thing, meaning it's
not an external file that's a problem.

I appreciate any ideas.

TIA

Knox

Reply to this Message

Pieter Wijnen - 30 Mar 2005 19:56 GMT

There's a broken reference in your distributed db.
Either you are using a library not included in the runtime and /or there's a
mismatch between versions
of a "standard" Dll (ServicePack difference)
At least in the old days (haven't made any since '97). Access Packaging
Wizard relied on a set of Dll's stored in an alternate location than the
one's in use by Access (full-blown) - causing this kind of erata.

HTH

Pieter

>I had a runtime distributed program that was working fine. I made what I
>thought was a minor upgrade to it, not even touching the affected part.
[quoted text clipped - 14 lines]
>
> Knox

Reply to this Message

Knox - 30 Mar 2005 21:43 GMT

Thank you...

It seems like it's something where the Format() function lives. Any ideas
on what library has that? I understand generally the concept of libraries,
but it's something I know nothing about as far as Access goes.

Knox

> There's a broken reference in your distributed db.
> Either you are using a library not included in the runtime and /or there's
[quoted text clipped - 26 lines]
>>
>> Knox

Reply to this Message

George Nicholson - 31 Mar 2005 02:52 GMT

One hallmark of a reference problem is when Access seems to have taken
stupid pills and can't understand basic VB things, like Right(), Left(), (or
Format()?), etc. That doesn't mean that the problem is with the VBA library.
In fact, it almost never is. This can make the resulting error message a
bit misleading. You'll need to check all your references. You might want to
check out Doug Steele's references page:

http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

HTH,

Signature

George Nicholson

Remove 'Junk' from return address.

> Thank you...
>
[quoted text clipped - 33 lines]
>>>
>>> Knox

Reply to this Message

Knox - 04 Apr 2005 11:58 GMT

Thank you. That sounds very helpful. I will be a while getting to the
problem, but appreciate your input. That's exactly the way I feel about it:
Access took stupid pills. I guess that should be on the wish list for
Access 2006, the process for distributing runtime checks to see if you're
distributing everything you need.

Thanks,

Knox

> One hallmark of a reference problem is when Access seems to have taken
> stupid pills and can't understand basic VB things, like Right(), Left(),
[quoted text clipped - 44 lines]
>>>>
>>>> Knox

Reply to this Message