schedule updates of database

[vasanth kumar]

Hi,

I am using MS Access as database. I need to update the table on the 1st
day of every quarter. Is there anyway to achieve this in MSAccess.

Regards,
Vasanth

 

[Joseph Meehan]

Hi,

I am using MS Access as database. I need to update the table on
the 1st day of every quarter. Is there anyway to achieve this in
MSAccess.

Regards,
Vasanth

Where is the data coming from to do the update?

 

[vasanth kumar]

I just want to increase values of few fields. (this is part of leave
database management. every quarter each employee gets quota of leaves).
I made a batch file to update the databse. this is launching MSAccess
Application. I just want this happen in the background. but this gives a
prompt confirming the addition of data rows.

"C:\Progra~1\Micros~2\OFFICE11\msaccess.exe d:\scratch\db.mdb /x macro1" is
the command in my batch file
----------------------------

 

[Joseph Meehan]

I just want to increase values of few fields. (this is part of leave
database management. every quarter each employee gets quota of
leaves).
I made a batch file to update the databse. this is launching MSAccess
Application.

And after Access is launched, what is adding the data?

I just want this happen in the background. but this
gives a prompt confirming the addition of data rows.

Maybe we can trap the messages or turn them off.

 

[Cameron Sutherland]

If you are using Macros (sounds like you are) include the
SetWarnings Action just before you run your queries. Turn
them Off then put the same line after your queires when
they are done and turn them back on. This SetWarnings only
deals with the update/add/delete query messages and no
other such as error messages.

If you are running it in code try:
SetWarnings False
<update quries here>
SetWarnings True
-Cameron Sutherland

 

[vasanth kumar]

I have a macro, it has an SQL statement. I scheduled this by OS. so it adds
rows, but gives me some confirmation Messages. How to turn off these
messages. I hope it is clear about, "where from the data is coming & what is
adding data". let me know if u have any queries

 

[Douglas J. Steele]

In a macro, you can use SetWarnings No before you run the SQL, and
SetWarnings Yes after.

In VBA code, this would be DoCmd.SetWarnings False before, and
DoCmd.SetWarnings True after. However, you'd be better served in VBA code by
using CurrentDb().Execute strSQL, dbFailOnError instead, espcially if you're
running this unattended, because that will allow you to trap any errors that
might occur.