I have a problem w/ calculated field in A97 query...

[MLH]

MyLocPhone: Format$([LocPhone],"(@@@) @@@-@@@@")

The above expression is a field in a select query. On one XP box
(the dev box, of course). It works fine. On two other XP boxen -
it fails saying "Function isn't available in expressions in query
expression ..." ==> citing the MyLocPhone: Format$([LocPhone]...
as the problem.

The query is evaluated on-click of a command button. If it returns
records, there are things to be done. I have installed the A97 runtime
app onto the 3 XP machines. Of course, the target machines where
it is intended to run as a live app are the one's causing me grief. It
is extremely frustrating - really, it is.

My reference: qryPendingUnprintedOutboundCorrespondenceENF-260ies

[Rick Brandt]

MLH wrote:

MyLocPhone: Format$([LocPhone],"(@@@) @@@-@@@@")

The above expression is a field in a select query. On one XP box
(the dev box, of course). It works fine. On two other XP boxen -
it fails saying "Function isn't available in expressions in query
expression ..." ==> citing the MyLocPhone: Format$([LocPhone]...
as the problem.

The query is evaluated on-click of a command button. If it returns
records, there are things to be done. I have installed the A97 runtime
app onto the 3 XP machines. Of course, the target machines where
it is intended to run as a live app are the one's causing me grief. It
is extremely frustrating - really, it is.

My reference: qryPendingUnprintedOutboundCorrespondenceENF-260ies

You have a missing or broken reference. Open a code window on the problem PC
and then look at Tools - References. One of the "checked" ones will have the
word "MISSING" after it.

That reference either needs to be removed from the file or fixed on that PC.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[MLH]

I might also mention that it happens on a Win98 box
that I installed the A97 runtime app onto.

[MLH]

Very promising. I'll check it out & get back with you. Thx!
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

You have a missing or broken reference. Open a code window on the problem PC
and then look at Tools - References. One of the "checked" ones will have the
word "MISSING" after it.

That reference either needs to be removed from the file or fixed on that PC.

[MLH]

AnsyrPrint Type 1.0 Library was the one with "missing" beside it.
You hit the nail right on the head.

1) How do I obtain what's missing?
2) Does it require installation procedure more complex than simply
copying a file to a specified location on the target machines?

The machine I tested was the Win98 machine. I won't be able to
examine the others until tomorrow.

[MLH]

Regarding the AnsyrPrint Type 1.0 Library...

I think it has something to do with the JAWS PDF Editor.
Hell, I don't even want that thing. I have a JAWS PDF
Creator printer device as one of my installed printers. I
must have their editor (at least an expired evaluation
copy) on there too. I'm pretty sure that's the editor. Yep.
Sure enough, I checked my desktop and I have an icon
that launches "C:\Program Files\Jaws PDF Editor\" on
there.

Well. That's it. I'm lost now. Hope you can help. I am
confused as to how A97 latched onto this thing and
tries to ship out references to it along with my runtime
distributions. Oh well. I guess I need to know how to
instruct Access to forget about this thing - forget that
it even exists. Maybe Access is getting its cues from
the OS or something. Gosh, I'm lost.

[Rick Brandt]

MLH wrote:

Regarding the AnsyrPrint Type 1.0 Library...

I think it has something to do with the JAWS PDF Editor.
Hell, I don't even want that thing. I have a JAWS PDF
Creator printer device as one of my installed printers. I
must have their editor (at least an expired evaluation
copy) on there too. I'm pretty sure that's the editor. Yep.
Sure enough, I checked my desktop and I have an icon
that launches "C:\Program Files\Jaws PDF Editor\" on
there.

Well. That's it. I'm lost now. Hope you can help. I am
confused as to how A97 latched onto this thing and
tries to ship out references to it along with my runtime
distributions. Oh well. I guess I need to know how to
instruct Access to forget about this thing - forget that
it even exists. Maybe Access is getting its cues from
the OS or something. Gosh, I'm lost.

Just uncheck it.

If you open a new blank A97 file and look at the references you will see the 3
or 4 default ones. In my opinion, those are the only ones you should ever have
set in an app that needs to be distributed to other users.

Additional references can get checked when you are experimenting with various
things duriong development. It is always a good idea to periodically check them
and eliminate any extra ones.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[MLH]

Thanks a lot, Rick. I'll have a go at that.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Just uncheck it.

If you open a new blank A97 file and look at the references you will see the 3
or 4 default ones. In my opinion, those are the only ones you should ever have
set in an app that needs to be distributed to other users.

Additional references can get checked when you are experimenting with various
things duriong development. It is always a good idea to periodically check them
and eliminate any extra ones.

[MLH]

Yes, well now, that did the trick. I installed a temporary copy
of Access 97 onto the Win98 box on which the runtime app
was installed and I put a copy of the SOURCE mdb file on
there too. Opening the mdb and one of its modules, Tools,
References revealed the problem.

So I went back to the development box, opened the SOURCE
mdb, unchecked the problematic reference, rebuilt the mde
file, copied the newly created mde to the Win98 box runtime
appdir - overwriting the old. I opened it - problem gone. I do
appreciate that.

Of course, dbl-clicking the runtime application icon on the
desktop now results in MS Access 97 splash screen being
displayed during the launch. That will go away after I remove
the copy of A97 I installed onto the Win98 box, I'm sure. But
I really would like to know how to circumvent this behavior,
as it catches me by surprise sometimes when I install a runtime
app onto a customer machine already having A97 installed.

My application icon Target: string looks like this...
"C:\Program Files\TowPack\TowPack.mde"
and its Start In: string like this...
"C:\Program Files\TowPack"

I'm certain the installation of A97 changed the file association
for mde files to be launched with A97's msaccess.exe in
C:\Program Files\Microsoft Office\Office\ instead of whatever
it was using before. So, how could I modify my runtime app's
Target: string to launch the way it was launching before I
installed A97 last night?

[Rick Brandt]

MLH wrote:

Of course, dbl-clicking the runtime application icon on the
desktop now results in MS Access 97 splash screen being
displayed during the launch. That will go away after I remove
the copy of A97 I installed onto the Win98 box, I'm sure. But
I really would like to know how to circumvent this behavior,
as it catches me by surprise sometimes when I install a runtime
app onto a customer machine already having A97 installed.

My application icon Target: string looks like this...
"C:\Program Files\TowPack\TowPack.mde"
and its Start In: string like this...
"C:\Program Files\TowPack"

I'm certain the installation of A97 changed the file association
for mde files to be launched with A97's msaccess.exe in
C:\Program Files\Microsoft Office\Office\ instead of whatever
it was using before. So, how could I modify my runtime app's
Target: string to launch the way it was launching before I
installed A97 last night?

Unless you go to some length to prevent it you won't have two separate instances
of the MSAccess.exe file on the machine. The runtime installer will not install
the runtime if Access 97 is already present and the Office 97 installer will use
the same folder and file that the runtime created if the runtime install is done
first.

What you need is the /Runtime command line argument in your shortcut if you want
the app to run in the "runtime environment" even when a fully licensed copy is
present.

If you place your own BMP file in the same folder as your mdb and give it the
same name as your mdb (other than extension) then it will display that when you
app is opened instead of the Office splash screen.

As stated previously you need to recreate your setup package and use the options
provided for a proper shortcut to be created. It should not simply be a
shortcut pointing at the mdb file.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[MLH]

<censored>
Yeah, you're right. I've gotta do that. I'll get around to it this
weekend hopefully. Have a good 4th.

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

As stated previously you need to recreate your setup package and use the options
provided for a proper shortcut to be created. It should not simply be a
shortcut pointing at the mdb file.