turn off warning message in mde

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Novice User - 01 Apr 2008 20:40 GMT

Hi

I hope someone can tell me how to do this. I have an append query that runs
when I open a form. While working with the full version of Access (ver 2002)
I have turned off the warnings for action queries - but when I create the mde
I get the warning using the Access Viewer.

Also, is there a way for the MDE to retain the login information so the user
doesn't have to type it? My report is linking to my accounting tables vie
obdc so I have to type a user id (no password) to login in - can this be
automated?

Thanks for your help

Reply to this Message

Albert D. Kallal - 01 Apr 2008 20:50 GMT

There are two solutions that I often use to solve this problem:

1), in place of docmd.RunSql, use

currentdb.Execute strSql

2) simply execute a set warnings command right before you run the runSql.

eg:
DoCmd.SetWarnings False

DoCmd.RunSQL "drop table qtemp"

MySql = "SELECT * INTO qtemp FROM qryDestSeats where " & buildwhere
DoCmd.RunSQL MySql

DoCmd.SetWarnings True

For the most part, I now use the currentDb.Execute method...

Signature

Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com

Reply to this Message

Novice User - 01 Apr 2008 21:51 GMT

Thank you - that took care of it.

Any ideas on passing the UserID?

> There are two solutions that I often use to solve this problem:
>
[quoted text clipped - 15 lines]
>
> For the most part, I now use the currentDb.Execute method...

Reply to this Message

Klatuu - 01 Apr 2008 21:24 GMT

Albert answered the first question. As to the user login, if you mean the
network login, you can get the code at this link:

http://www.mvps.org/access/api/api0008.htm

Signature

Dave Hargis, Microsoft Access MVP

> Hi
>
[quoted text clipped - 9 lines]
>
> Thanks for your help

Reply to this Message

Novice User - 01 Apr 2008 22:11 GMT

Thank you for your reply - it is not the network login, but the login for the
Accounting software package that I am linking to.

> Albert answered the first question. As to the user login, if you mean the
> network login, you can get the code at this link:
[quoted text clipped - 14 lines]
> >
> > Thanks for your help

Reply to this Message

Klatuu - 01 Apr 2008 22:51 GMT

You could still use the API to determine who is logged on.
Then create a table with userID and the accounting package login. Then you
call use a DLookup to find the password for the user who is logged in.

Signature

Dave Hargis, Microsoft Access MVP

> Thank you for your reply - it is not the network login, but the login for the
> Accounting software package that I am linking to.
[quoted text clipped - 17 lines]
> > >
> > > Thanks for your help

Reply to this Message

Albert D. Kallal - 02 Apr 2008 00:44 GMT

> Thank you for your reply - it is not the network login, but the login for
> the
> Accounting software package that I am linking to.

Hum, I think in this case, I would simply store this info in a table.
Perhaps even a one record table. That way, you make the box that prompts the
user as a bound form to a table. If the form is bound then next time the
user opens that form, the old informaton will be retained....

Signature

Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com

Reply to this Message