Can I assign an active X calander to a query

[Andreas]

Create a folder in your "C:" drive.
Call it "Database" (without the quotes).
Copy the database (.mdb) into that folder.
Copy the workgroup (.mdw) into that folder.

Create a shortcut as follows:
"C:\Program Files\Microsoft Office\Office\MSACCESS.exe"
"C:\Database\YourDatabaseName.mdb" /WRKGRP
"C:\Database\YourWorkgroupName.mdw"

Ensure the workgroup file is the one the wizard created and not the
original one. Ensure you type the above with the quotes as shown without
pressing the "Enter" key inbetween. Ensure the file MSACCESS.exe is in
the directory as per above - if not, modify the path appropriately.

If this doesn't work, I am out of ideas.
You can make Access look at the workgroup file permanently but then you
will have issues with any other databases that may be in use or created
later, therefore I won't go there.

As far as security is concerned, this is a whole discussion in it's own
right.

My main concern at this point is that if you are going to have multiple
users and the database is not on the server, and anyone makes changes,
the others will not be able to see those changes as everyone has their
own local copy, which is not shared.

Regards,
Andreas

 

[Guest]

Thanks for that and all your prevous help. The database needs to be local, to
limit the input to just one authorised user at one site. I shall try your
latest advice.

 

[Guest]

Does anybody know how to stop the screen from flickering when switching
between forms. I know in Excel the code is Application.ScreenUpdating.False,
I have tried using this in Access without success. Is there a way of closing
one form, when another is opened?

 

[Rick Brandt]

Does anybody know how to stop the screen from flickering when
switching between forms. I know in Excel the code is
Application.ScreenUpdating.False, I have tried using this in Access
without success. Is there a way of closing one form, when another is
opened?

Application.Echo False
(do some stuff)
Application.Echo True

Make sure you include an error trap that also sets the Echo back to true or your
user could get stuck with an app that won't update the screen.

 

[Guest]

Can anyone help with this.
When I enter a date onto the database, I need to convert the date to a year
and week format. I have two problems.

The first is the year and week becomes say 20059, but I need it to be
200509, how can I get the extra nought before the 9.
When I enter the date, the data baseconverts it ok, but is currently 1 week
out of sync. ie, 07/02/05 convers to week 11 and not week 10......any ideas
please.

 

[Guest]

How can I set the work week to be Monday to Sunday, or even Sunday to Saturday?

Can anybody help please?

 

[Douglas J. Steele]

Functions like DatePart and Format (both of which can be used to calculate
week) have two optional arguments that let you specify the first day of the
week (use vbMonday, or 2 in your case) and first week of the year. Check the
Help file for details.

 

[Guest]

That's great and I have mangaged to do that now, one other point, the weeks
are out of sync by one, ie, 200505, should be 200504, any ideas on why.

 

[Douglas J. Steele]

Not without knowing what date you're passing to get that value and how
you're calculating it...

 

[Guest]

Hi,

The date is entered as say 04/04/2005 and then datepart to give year number
and datepart to give weeknumber. These are then merge and the output is
200515 and not 200514 as it should be.If I use the formula on the week to be
WK: Format(DatePart("ww",[DATE],2)-1,"00") correct weekdate will be 14. I
would appreciate any help you can give me.

 

[Douglas J. Steele]

Sounds as though you need to play with the fourth parameter that specifies
the first week of the year.

Acceptable values are:

vbFirstJan1 (1) Start with week in which January 1 occurs
(default).
vbFirstFourDays (2) Start with the first week that has at least four days
in the new year.
vbFirstFullWeek (3) Start with first full week of the year.

WK: Format(DatePart("ww",[DATE],2,2)-1,"00") returns 14, but you might want
to test some other dates and with the other parameter values.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

Hi,

The date is entered as say 04/04/2005 and then datepart to give year
number
and datepart to give weeknumber. These are then merge and the output is
200515 and not 200514 as it should be.If I use the formula on the week to
be
WK: Format(DatePart("ww",[DATE],2)-1,"00") correct weekdate will be 14. I
would appreciate any help you can give me.

Not without knowing what date you're passing to get that value and how
you're calculating it...

 

[Guest]

Can anyone help me with this formula in a query,

BASIC PAY: IIf([DAY]<>"SAT" Or "SUN",[PAID HRS] = 8,0) in my mind it looks
correct but it obviously it isn't. What is the correct way to use an "OR"
function.Any help would be gratefully appreciated.

Sounds as though you need to play with the fourth parameter that specifies
the first week of the year.

Acceptable values are:

vbFirstJan1 (1) Start with week in which January 1 occurs
(default).
vbFirstFourDays (2) Start with the first week that has at least four days
in the new year.
vbFirstFullWeek (3) Start with first full week of the year.

WK: Format(DatePart("ww",[DATE],2,2)-1,"00") returns 14, but you might want
to test some other dates and with the other parameter values.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

Hi,

The date is entered as say 04/04/2005 and then datepart to give year
number
and datepart to give weeknumber. These are then merge and the output is
200515 and not 200514 as it should be.If I use the formula on the week to
be
WK: Format(DatePart("ww",[DATE],2)-1,"00") correct weekdate will be 14. I
would appreciate any help you can give me.

Not without knowing what date you're passing to get that value and how
you're calculating it...

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)



That's great and I have mangaged to do that now, one other point, the
weeks
are out of sync by one, ie, 200505, should be 200504, any ideas on why.

:

Functions like DatePart and Format (both of which can be used to
calculate
week) have two optional arguments that let you specify the first day
of
the
week (use vbMonday, or 2 in your case) and . Check
the
Help file for details.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)



How can I set the work week to be Monday to Sunday, or even Sunday
to
Saturday?

Can anybody help please?


:

Can anyone help with this.
When I enter a date onto the database, I need to convert the date
to a
year
and week format. I have two problems.

The first is the year and week becomes say 20059, but I need it to
be
200509, how can I get the extra nought before the 9.
When I enter the date, the data baseconverts it ok, but is
currently 1
week
out of sync. ie, 07/02/05 convers to week 11 and not week
10......any
ideas
please.


:

cel504 wrote:
Does anybody know how to stop the screen from flickering when
switching between forms. I know in Excel the code is
Application.ScreenUpdating.False, I have tried using this in
Access
without success. Is there a way of closing one form, when
another
is
opened?

Application.Echo False
(do some stuff)
Application.Echo True

Make sure you include an error trap that also sets the Echo back
to
true or your
user could get stuck with an app that won't update the screen.

 

[MGFoster]

Can anyone help me with this formula in a query,

BASIC PAY: IIf([DAY]<>"SAT" Or "SUN",[PAID HRS] = 8,0) in my mind it looks
correct but it obviously it isn't. What is the correct way to use an "OR"
function.Any help would be gratefully appreciated.

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

Like this:

Basic Pay: IIf([Day]<>"SAT" OR [Day]<>"SUN", 8, 0)

What are you trying to do, an UPDATE? Try the following to just change
the Paid Hrs for Mon-Fri days:

UPDATE table_name
SET [Paid Hrs] = 8
WHERE [Day] Not In ("Sat", "Sun")

Or, for all days in one go:

UPDATE table_name
SET [Paid Hrs] = IIf([Day] Not In ("Sat","Sun"), 8, 0)

--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

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

iQA/AwUBQl7WzoechKqOuFEgEQJyWQCeM1zvwKpQxFJeD7nvlObsMaZBdPYAnixO
9qCc+SlfhYAuC1O8MT7OkcJg
=W4VP
-----END PGP SIGNATURE-----