By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,647 Members | 1,124 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,647 IT Pros & Developers. It's quick & easy.

VERY simple application fails to start

P: n/a
Environment: Windows XP, Access 2000 ADP, SQL Server 2000, all at latest
service packs.
We built a new machine, and it fails to run even the simplest ADP. I created
an AutoExec macro with one line: RunCode - InitApplication(), and one public
function InitApplication() with a "Hello World" messagebox. That's it.
When trying to start the app, we get "The expression you entered has a
function name that TestApp can't find". This is followed by an "Action
Failed" dialog, with MacroName=AutoExec, Action=RunCode, and
Arguments=InitApplication(). The "Halt" button is the only option.

Has anyone ever seen this behavior, or cares to speculate about what could
cause it?

I'm thinking it's something environmental with that machine. 20 other
workstations run the app just fine.
Nov 13 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sounds like a references problem. In the VBA window select Tools >
References. Check that the VBA (Visual Basic for Applications) is
checked. Check that there aren't any MISSING entries that need to be
unchecked.
--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQtf+Z4echKqOuFEgEQIA0gCgwdTn/R35W4j5YU0GJEGB6e3q0lUAmwfs
BeZE6l+J4K8MYAaFeBKrFHo5
=OYSY
-----END PGP SIGNATURE-----
Tom van Stiphout wrote:
Environment: Windows XP, Access 2000 ADP, SQL Server 2000, all at latest
service packs.
We built a new machine, and it fails to run even the simplest ADP. I created
an AutoExec macro with one line: RunCode - InitApplication(), and one public
function InitApplication() with a "Hello World" messagebox. That's it.
When trying to start the app, we get "The expression you entered has a
function name that TestApp can't find". This is followed by an "Action
Failed" dialog, with MacroName=AutoExec, Action=RunCode, and
Arguments=InitApplication(). The "Halt" button is the only option.

Has anyone ever seen this behavior, or cares to speculate about what could
cause it?

I'm thinking it's something environmental with that machine. 20 other
workstations run the app just fine.

Nov 13 '05 #2

P: n/a
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sounds like a references problem. In the VBA window select Tools >
References. Check that the VBA (Visual Basic for Applications) is
checked. Check that there aren't any MISSING entries that need to be
unchecked.
--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQtf+Z4echKqOuFEgEQIA0gCgwdTn/R35W4j5YU0GJEGB6e3q0lUAmwfs
BeZE6l+J4K8MYAaFeBKrFHo5
=OYSY
-----END PGP SIGNATURE-----
Tom van Stiphout wrote:
Environment: Windows XP, Access 2000 ADP, SQL Server 2000, all at latest
service packs.
We built a new machine, and it fails to run even the simplest ADP. I created
an AutoExec macro with one line: RunCode - InitApplication(), and one public
function InitApplication() with a "Hello World" messagebox. That's it.
When trying to start the app, we get "The expression you entered has a
function name that TestApp can't find". This is followed by an "Action
Failed" dialog, with MacroName=AutoExec, Action=RunCode, and
Arguments=InitApplication(). The "Halt" button is the only option.

Has anyone ever seen this behavior, or cares to speculate about what could
cause it?

I'm thinking it's something environmental with that machine. 20 other
workstations run the app just fine.

Nov 13 '05 #3

P: n/a
On Fri, 15 Jul 2005 18:20:18 GMT, MGFoster <me@privacy.com> wrote:

Not this time.
The file was created on the "bad" machine, and it just had the 4
standard references. Nothing broken. Code compiled fine.
Per Google I removed and recreated the references. Also checked into
the Sandbox setting.
Btw, I could run InitApplication just fine from the Immediate window.

What I finally discovered (just before I was going to give up and tell
them to rebuild the machine) was that installing Jet 4.0 SP8 did the
trick.

-Tom.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sounds like a references problem. In the VBA window select Tools >
References. Check that the VBA (Visual Basic for Applications) is
checked. Check that there aren't any MISSING entries that need to be
unchecked.


Nov 13 '05 #4

P: n/a
On Fri, 15 Jul 2005 18:20:18 GMT, MGFoster <me@privacy.com> wrote:

Not this time.
The file was created on the "bad" machine, and it just had the 4
standard references. Nothing broken. Code compiled fine.
Per Google I removed and recreated the references. Also checked into
the Sandbox setting.
Btw, I could run InitApplication just fine from the Immediate window.

What I finally discovered (just before I was going to give up and tell
them to rebuild the machine) was that installing Jet 4.0 SP8 did the
trick.

-Tom.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sounds like a references problem. In the VBA window select Tools >
References. Check that the VBA (Visual Basic for Applications) is
checked. Check that there aren't any MISSING entries that need to be
unchecked.


Nov 13 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.