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

Access Runtime and Security

P: n/a
Hi,

I have a secured database that runs fine on the computer the database is
installed on. I have several workstations with access runtime installed
that also need access to the database. Access runtime runs fine when
accessing an unsecured version of the database. However once the database
was secured it generates a runtime error after asking for the user and
password and won't open. The shortcut to the secured database is:

"path to msaccess runtime on local machine" /wrkgrp "path to mdw file on
remote machine" "path to mdb on remote machine"

I have also tried accessing the database with the mdw file placed on the
local machine as well, with the same results.

Is Access 2000 runtime not capable of running a secured database or are
there some other issues that I have overlooked?

Thanks in advance for any help provided
Nathan Bloom

Nov 13 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
On Sat, 29 May 2004 18:56:57 GMT, "Nathan Bloom"
<na*******@earthlink.net> wrote:

Yes, you overlooked an issue: telling us which of the hundreds of
possible runtime errors you are getting, and telling us what line of
code generates it.

My guess: you may have a references problem totally unrelated to
security.

-Tom.

Hi,

I have a secured database that runs fine on the computer the database is
installed on. I have several workstations with access runtime installed
that also need access to the database. Access runtime runs fine when
accessing an unsecured version of the database. However once the database
was secured it generates a runtime error after asking for the user and
password and won't open. The shortcut to the secured database is:

"path to msaccess runtime on local machine" /wrkgrp "path to mdw file on
remote machine" "path to mdb on remote machine"

I have also tried accessing the database with the mdw file placed on the
local machine as well, with the same results.

Is Access 2000 runtime not capable of running a secured database or are
there some other issues that I have overlooked?

Thanks in advance for any help provided
Nathan Bloom


Nov 13 '05 #2

P: n/a
Sorry, The error is:

Execution of this application has stopped due to a run-time error.
This application can't continue and will be shut down.

It a appears in a message box with an OK button. There isn't any error
number or line of code referenced. Once again, it only happens on machines
with Access Runtime and not on machines with full versions of Access.

Thanks again in advance for any help offered.
Nathan Bloom

"Tom van Stiphout" <to*****@no.spam.cox.net> wrote in message
news:j5********************************@4ax.com...
On Sat, 29 May 2004 18:56:57 GMT, "Nathan Bloom"
<na*******@earthlink.net> wrote:

Yes, you overlooked an issue: telling us which of the hundreds of
possible runtime errors you are getting, and telling us what line of
code generates it.

My guess: you may have a references problem totally unrelated to
security.

-Tom.

Hi,

I have a secured database that runs fine on the computer the database is
installed on. I have several workstations with access runtime installed
that also need access to the database. Access runtime runs fine when
accessing an unsecured version of the database. However once the databasewas secured it generates a runtime error after asking for the user and
password and won't open. The shortcut to the secured database is:

"path to msaccess runtime on local machine" /wrkgrp "path to mdw file on
remote machine" "path to mdb on remote machine"

I have also tried accessing the database with the mdw file placed on the
local machine as well, with the same results.

Is Access 2000 runtime not capable of running a secured database or are
there some other issues that I have overlooked?

Thanks in advance for any help provided
Nathan Bloom

Nov 13 '05 #3

P: n/a
On Sun, 30 May 2004 09:51:17 GMT, "Nathan Bloom"
<na*******@earthlink.net> wrote:

I entered this error message at search.microsoft.com and got several
promising leads. Go ahead and investigate those first.

Also, you still haven't told us at which line of code this error
occurs. Even in runtime applications you can perform some level of
debugging, such as by temporarily adding code that will write some
output to a log file (and close that file after each write, so you are
sure the file contains all the data collected so far when the app
terminates).

-Tom.

Sorry, The error is:

Execution of this application has stopped due to a run-time error.
This application can't continue and will be shut down.

It a appears in a message box with an OK button. There isn't any error
number or line of code referenced. Once again, it only happens on machines
with Access Runtime and not on machines with full versions of Access.

Thanks again in advance for any help offered.
Nathan Bloom

"Tom van Stiphout" <to*****@no.spam.cox.net> wrote in message
news:j5********************************@4ax.com.. .
On Sat, 29 May 2004 18:56:57 GMT, "Nathan Bloom"
<na*******@earthlink.net> wrote:

Yes, you overlooked an issue: telling us which of the hundreds of
possible runtime errors you are getting, and telling us what line of
code generates it.

My guess: you may have a references problem totally unrelated to
security.

-Tom.

>Hi,
>
>I have a secured database that runs fine on the computer the database is
>installed on. I have several workstations with access runtime installed
>that also need access to the database. Access runtime runs fine when
>accessing an unsecured version of the database. However once thedatabase >was secured it generates a runtime error after asking for the user and
>password and won't open. The shortcut to the secured database is:
>
>"path to msaccess runtime on local machine" /wrkgrp "path to mdw file on
>remote machine" "path to mdb on remote machine"
>
>I have also tried accessing the database with the mdw file placed on the
>local machine as well, with the same results.
>
>Is Access 2000 runtime not capable of running a secured database or are
>there some other issues that I have overlooked?
>
>Thanks in advance for any help provided
>Nathan Bloom
>
>


Nov 13 '05 #4

P: n/a
"Nathan Bloom" <na*******@earthlink.net> wrote:
Execution of this application has stopped due to a run-time error.
This application can't continue and will be shut down.

It a appears in a message box with an OK button. There isn't any error
number or line of code referenced. Once again, it only happens on machines
with Access Runtime and not on machines with full versions of Access.


I suspect this problem is some code that doesn't have an error handling. In the full
version of Access you'll get the message with a prompt asking if you want to debug
the code or cancel. (Or something similar.) In the runtime you get the above
message.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Nov 13 '05 #5

P: n/a
Tom,

Thank you for your help. I placed some message boxes at various points in
the main menus opening code. When I was setting up the security, I
commented out certain parts of the opening code to allow quicker testing. I
neglected to do this in a module that is called during startup that requires
certain values to be passed to it. The message boxes quickly pointed to my
oversight. Thanks again for your suggestion.

Nate
"Tom van Stiphout" <to*****@no.spam.cox.net> wrote in message
news:gs********************************@4ax.com...
On Sun, 30 May 2004 09:51:17 GMT, "Nathan Bloom"
<na*******@earthlink.net> wrote:

I entered this error message at search.microsoft.com and got several
promising leads. Go ahead and investigate those first.

Also, you still haven't told us at which line of code this error
occurs. Even in runtime applications you can perform some level of
debugging, such as by temporarily adding code that will write some
output to a log file (and close that file after each write, so you are
sure the file contains all the data collected so far when the app
terminates).

-Tom.

Sorry, The error is:

Execution of this application has stopped due to a run-time error.
This application can't continue and will be shut down.

It a appears in a message box with an OK button. There isn't any error
number or line of code referenced. Once again, it only happens on machineswith Access Runtime and not on machines with full versions of Access.

Thanks again in advance for any help offered.
Nathan Bloom

"Tom van Stiphout" <to*****@no.spam.cox.net> wrote in message
news:j5********************************@4ax.com.. .
On Sat, 29 May 2004 18:56:57 GMT, "Nathan Bloom"
<na*******@earthlink.net> wrote:

Yes, you overlooked an issue: telling us which of the hundreds of
possible runtime errors you are getting, and telling us what line of
code generates it.

My guess: you may have a references problem totally unrelated to
security.

-Tom.
>Hi,
>
>I have a secured database that runs fine on the computer the database is >installed on. I have several workstations with access runtime installed >that also need access to the database. Access runtime runs fine when
>accessing an unsecured version of the database. However once the

database
>was secured it generates a runtime error after asking for the user and
>password and won't open. The shortcut to the secured database is:
>
>"path to msaccess runtime on local machine" /wrkgrp "path to mdw file on >remote machine" "path to mdb on remote machine"
>
>I have also tried accessing the database with the mdw file placed on the >local machine as well, with the same results.
>
>Is Access 2000 runtime not capable of running a secured database or are >there some other issues that I have overlooked?
>
>Thanks in advance for any help provided
>Nathan Bloom
>
>

Nov 13 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.