The attached shows how you can have a table with designated email addresses in a table and loop through that table sending an email to all those email addresses (and/or attach a report to each email.) This example uses the SendObject command for use with Outlook. (Note: the example loops through the emailing table sending separate emails on each email address record verses concatenating all the email addresses into one string and sending one email.)

Attached is a word document showing the reserved words in MSAccess/SQL Server you should never use for field/table names. (Note: the 2nd document is by Baird Technology Group - Copyright© 1999 - 2007 Baird Technology Group, Inc. All Rights Reserved.)

URL on Microsoft.com is http://support.microsoft.com/kb/286335

or if you are a real masochist try the search results for 'reserved words access' on MSDN
http://search.microsoft.com/results.aspx?mkt=en-GB&setlang=en-GB&q=reserved+words+access

The attached contains some vba code I've used to search for useful information in the Active Directory.

Here are some additional comments from grafiksinc on the code in this example:

I only use a few parts of the entire thing specifically the part about getting user information from AD.

I quote another fellow
"realistically to get your import to run a bit faster , you'd probably be better off running an INSERT INTO SQL statement:"

INSERT INTO AD_User (UserName, FirstName, LastName, BusinessPhone, DisplayName, LogonName)
SELECT Name,givenName,SN,telephonenumber,displayname,sAMA ccountName
FROM 'LDAP://OU=,DC=,
WHERE objectCategory='user'"

It was true the way you wrote it worked but this did help it speed up. In my case I have about 2000+ users I am importing.

NOTE:********
I excluded the LDAP just know that you need to add in your own domain.

A few extra notes:
1. This could not work for me because the Value list in a combo box
is limited to like 30 something thousand characters.
and for 2000+ users this is reached.

But if your users are less than lets say 100 this should work fine for you.

2. I wanted to see 6 columns in AD but you can change that to whatever
suits. You can also and change the SQL to get other info that you need from AD

Private Sub lstUsers_GotFocus()
'*****************************************
'*Connects To AD and sets search criteria*
'*****************************************
'On Error Resume Next
Dim rs As ADODB.Recordset
Dim strSql As String
Const ADS_SCOPE_SUBTREE = 2


Set objConnection = CreateObject("ADODB.Connection")
Set objCommand = CreateObject("ADODB.Command")
objConnection.Provider = "ADsDSOObject"
objConnection.Open "Active Directory Provider"
Set objCommand.ActiveConnection = objConnection
objCommand.Properties("Page Size") = 1000
objCommand.Properties("Searchscope") = ADS_SCOPE_SUBTREE

'************************************************* *********************
'*SQL statement on what OU to search and to look for User Objects ONLY*
'************************************************* *********************
objCommand.CommandText = _
"SELECT Name,givenName,SN,telephonenumber,displayname,sAMA ccountName " _
& "FROM 'LDAP://OU=,DC=' WHERE " _
& "objectCategory='user'"

'*************************************
'Adds records to list box
'*************************************
With Me!lstUsers
.RowSourceType = "Value List"
.ColumnCount = 6
End With

Set objrecordset = objCommand.Execute
With objrecordset
.MoveFirst
Do While Not .EOF
Me!lstUsers.AddItem .Fields("Name").Value & ";" & _
.Fields("GivenName").Value & ";" & _
.Fields("SN").Value & ";" & _
.Fields("telephonenumber").Value & ";" & _
.Fields("DisplayName").Value & ";" & _
.Fields("sAMAccountName").Value
.MoveNext
Loop
End With

objrecordset.Close
Set objrecordset = Nothing

End Sub

---------------------------------------------------------
Here is what this code will do,
On the form that you have now Add a text box for testing and name it
"last".

What the code does is, it looks at that field for the last name.

So, when you select the Combo it will search AD for only the users that
match the value that is in the text box names last.

It's faster and it only gets the data that is in use at the time.
There-fore no need to import AD users.

With all that said this is just one scenario but you could expand on
this potentially rather than have it say look at another text box but
make it look at itself possibly.


Code-------------------------------------------------------------------------------------------------------------
'*****************************************
'*Connects To AD and sets search criteria*
'*****************************************
'On Error Resume Next
Dim rs As ADODB.Recordset
Dim strSql As String
Const ADS_SCOPE_SUBTREE = 2
'On Error GoTo ADImportError
'Screen.MousePointer = 11

Set objConnection = CreateObject("ADODB.Connection")
Set objCommand = CreateObject("ADODB.Command")
objConnection.Provider = "ADsDSOObject"
objConnection.Open "Active Directory Provider"
Set objCommand.ActiveConnection = objConnection
objCommand.Properties("Page Size") = 1000
objCommand.Properties("Searchscope") = ADS_SCOPE_SUBTREE

'************************************************* *********************
'*SQL statement on what OU to search and to look for User Objects ONLY*
'************************************************* *********************
objCommand.CommandText = _
"SELECT SN, GivenName, sAMAccountName " _
& "FROM 'LDAP://OU=DC=' WHERE " _
& "objectCategory='user'" _
& "AND SN='" & Me!last & "'"


'*************************************
'Adds records to list box
'*************************************
With Me!lstUsers
.RowSourceType = "Value List"
.ColumnCount = 1
End With

Set objrecordset = objCommand.Execute
With objrecordset
.MoveFirst
Do While Not .EOF
Me!lstUsers.AddItem .Fields("SN").Value
'& ";" & _
'.Fields("GivenName").Value & ";" & _
'.Fields("SN").Value & ";" & _
'.Fields("telephonenumber").Value & ";" & _
'.Fields("DisplayName").Value & ";" & _
'.Fields("sAMAccountName").Value
.MoveNext
Loop
End With

objrecordset.Close
Set objrecordset = Nothing
Exit_ADImport:
Screen.MousePointer = 0
Exit Sub

ADImportError:
MsgBox Err.Description & " - " & Err.Number & Chr(13) & Chr(13) _
& "Unable to produce picklist. Report the above error to ITD."

Resume Exit_ADImport
End Sub

See posts here: Use form List Box to query Active Directory
for additional comments and details.
.
.

The attachment will calculate the Monthly, Quarterly, Semi-Annual, and Annual periods and dates given a start date and end date.

For example, if 1/1/07 and 12/31/08 are supplied and Semi-Annual is selected, the following will be written:

Period 1 - 1/1/07 to 6/30/07
Period 2 - 7/1/07 to 12/31/07
Period 3 - 1/1/08 to 6/30/08
Period 4 - 7/1/08 to 12/31/08

if 1/1/07 and 12/31/07 are supplied and Quarterly is selected, the following will be written:

Period 1 - 1/1/07 to 3/31/07
Period 2 - 4/1/07 to 6/30/07
Period 3 - 7/1/07 to 9/30/07
Period 4 - 10/1/07 to 12/31/07

It uses code to find the First Day Of Month and Last Day Of Month for the month of each period.

One of the Most Important subject in a Database is its Security. If you simply go to Tools > Startup > Display Database Window, and disable it then in next start up it won't show the Database Window but if someone Hold the Shift key when opening the database then it will be Bypassed! So your tables will be in reach.
This is important in Multi User Databases and especially in 2007 MS Access Version Databases which User Level Security System is omitted to don’t let Users to access Tables and change the data on purpose or not.
Here is a simple code to disable\enable Shift Key Bypassing.
You can set a password for opening the Form1 to let only the Administrator to enable Shift Bypass for edit reasons.
Be careful to make a back up of your Database first if you want to use this Code.

The attached has some examples of different methods on manipulating the form look. Both an MSAccess 2000 and 2003 format are supplied.

The examples utilize:
1. The FormInfo module (to remove the caption or maximize without TaskBar showing)
2. The ScreenSize module (to resize the form)
3. Module2 (removing the MSAccess background information)

See comments in the modules for manipulating the forms with additional parameters.

New version uploaded 11/1/07!!:

4. Example showing how to do a rounded edge form.
5. Example showing how to do a translucent form (which nicely fades in).

New version (FormManipulation2.zip) uploaded 11/13/07 (new):
1. Task Panel example
2. Fade In/Out
3. Cool button effects
4. Color bar
5. Drag and Drop example
6. Tip Help
7. Menu on Click
8. Alternating greenbar report


NOTE: I TAKE NO CREDIT FOR THESE EXAMPLES!! These are a collection I've put together which I've found from various websites.

I repeat, I take no credit (well maybe a little for putting them all together).

This is example code to disable/enable the mouse scroll wheel from: http://www.lebans.com/mousewheelonoff.htm.

***********
Note: Another technique which works very well (without needing ANY dll or mousewheel code) is to put this code in the OnCurrent event of the form:
docmd.gotorecord,,acfirst
This works when you're ONLY dealing with 1 record on the form and want to prevent users from scrolling to a new blank record accidently.
***********

The second attachment (NoScrollMouseWheel.Zip) is a form I designed but copied the appropriate code from the MouseWheelOnOff.zip, leaving out code (and the module) I found not needed to make the technique work. I did not design any of the mousewheel code and take no credit for it.

Note: You can also try this neat little trick without using ANY mousewheel code:

If you're only dealing with 1 record on a form (ie. you use criteria to return that 1 record) and want to prevent scrolling to a new record (but need to also allow additions to the form), in the form's OnCurrent Event add this code:

docmd.gotorecord,,acFirst

This has worked very well for me and if the user tries to use the scroll, it will automatically go back to the first record! (so the user can't accidently scroll to a blank record.)

Also see this post: DBForums Code Bank

A simple dlookup example showing how it's done in a query and on a form.

The attachment is a very basic crosstab example. The key thing in designing a crosstab type report is making it so that when new records are added to the table, you don't have to manually edit the report and add in a new column to show the new column of information. This can easily be done by making the subreport based on the crosstab query (not a subreport) as the report example illustrates. You'll also notice that you can adjust the column widths in the crosstab query which also reflect in the report.

Test out the example by adding/deleting records to the table and notice that you don't have to do anything to the report design.

The attached has multiple different techniques which include:

1. Exporting data example an MSAccess table to a csv, xls or dbf file.
2. You select the query and folder to export to (with ability to add a date stamp to the filename).
3. Browse button to select the folder to export the data to.
4. Having a report listing table with a view/print button (GolferGuy's technique).
5. Progress bar example and showing it in action.
6. Calendar control example and other things to make entering dates easier (all clicking).
7. Reports based off of date and other criteria.
8. Code (ADO) showing how to open a recordset off of date criteria.

and some other neat techniques.

This is similar to the other reports example in this code bank I've previously uploaded but I've updated some things and added some new features (don't ask me why I keep updating this stuff).

Enjoy.

The following attachment shows how you can do GIF animation in MSAccess.

To utilize the Microsoft Web Browser activeX control, you'll need to have Internet Explorer installed. The example uses the Microsoft Web Browser activeX control which is included in the IE installation. You should not need to register this activeX control.

You'll first need to populate the table with the GIF file locations (click the Populate GifLookup button). Once you've populated the table of your GIF file locations (which automatically searches for GIF files in the directory you specify - and also searches the sub-directories), you can then open the GIF viewer form to cycle through and view the GIF files it found.

This example can also be used to store other files in a table, not just gif files.

Note: You need to empty the dbo_GifLookup table first as this is currently populated with gif filenames which I have on my drive (see button on the Populate GifFiles form to empty this table).

Have fun.

The attached zip file shows how you can do some cool animation (a flaming torch in the background) and make some cool looking buttons in MSAccess. See the MSAccess mdb file in the zip file. Also, lots of different *.gif buttons supplied in the zip file for you to change to (or you can get them on any website).

here's a little demo on handling unbound forms (actually form-singular in the demo) prompted by two recent requests here.

NB: this is not the way i normally do it!
ordinarily i have my load/validate/save code in the edit form itself which gives max flexibility and (with copy/paste) max laziness, but also max code-lines.
for this demo i have tried to consolidate the load/save stuff in a module that should talk to any unbound form.
validation is left as an exercise for the user

this demo is work in progress but it already feels quite interesting - maybe something like it will find it's way into production stuff after a little more development.

it would be *WONDERFUL* to get any sort of feedback - improvements, criticisms, hatemail, whatever: all welcome via PM. i would be particularly happy to get code variations.

izy

Attached is an example of a form which transitions one color to another on a form. User color selection is saved in a table so each user can select their own background colors (and even the backcolors of the fields.)

There is also an example of a form which shows buttons with a rollover type affect and changes the pointer to a hand when hovered over the button.

when trying to allocate resources, instinct is to create a mess of recordsets, memory arrays, and loops.

this demo takes a SQL approach.

the real-world application (from which this demo is drawn) is 10x faster with the SQL approach compared with an earlier memory-array approach. apart from the need to devise a relatively ugly query, it is also way simpler to code.

DAO reference required.
db is A2K format

izy