Replies

Excellent idea, Drew.
Haven’t tried it out, but spotted a small typo: you should limit your loops to rs.Fields.Count – 1

Excellent idea, Drew.
Haven’t tried it out, but spotted a small typo: you should limit your loops to rs.Fields.Count – 1

Thanks Hans,
I’m still laughing that I did not see that myself . Please don’t tell anyone.

Wendell,
Permissions are set on groups (not users). The point is that a workgroup information file cannot be standard and unique to the customer at the same time. The name, org, and workgroup ID specified on creation of the workgroup information file is what makes it unique. If it is not unique but standard for the application then data belonging to one customer could easily be displayed/used by another customer (running the same application) using his own workgroup information file

Charlotte,
I understand that you distribute a copy of the same standard workgroup information file to each customer

(

Good work Mark. I agree that in some cases you have to secure the FE to make absolutely sure.

Good point, Wendell – though you don

Why bother securing the FE?
Securing the data in BE is the important thing in my opinion. I see little point in securing the FE provided you release it as an mde.
Then modules and forms are safe. Tables are linked to the BE, hence no danger there.
Use AllowBypassKey the proper way and users cannot get into the dbs by using the shift key.
So, why would you secure the FE?

I am sorry if I have confused you, Chico. To get right to the point: what I guess you need right now is this part of my code to avoid a reference to the Outlook Object Library:

‘ Define Outlook constants
Const olTo = 1
Const olCC = 2
Const olBCC = 3
Const olMailItem = 0
‘ Define Outlook objects
Dim objOutlook As Object
Dim objOutlookMsg As Object
Dim objOutlookRecip As Object
Dim objOutlookAttach As Object

as a replacement for your DIM objOutLook

I have looked at your code and think this may help you. If you use late binding then you do not need a reference to the Outlook Object Library in your Access application. I think this method will solve your problem.

Replace your Dim-statements defining the Outlook objects by the lines of code shown below:

‘****** start of code
‘ When you set Development = True you need to add a reference to
‘ the MS Outlook xx.x Object Library.
‘ When you set Development = False you don’t need the reference.
#Const Development = False
#If Development = True Then
‘ Define Outlook objects
Dim objOutlook As Outlook.Application
Dim objOutlookMsg As Outlook.MailItem
Dim objOutlookRecip As Outlook.Recipient
Dim objOutlookAttach As Outlook.Attachment
#Else
‘ Define Outlook constants
Const olTo = 1
Const olCC = 2
Const olBCC = 3
Const olMailItem = 0
‘ Define Outlook objects
Dim objOutlook As Object
Dim objOutlookMsg As Object
Dim objOutlookRecip As Object
Dim objOutlookAttach As Object
#End If
‘ ****** end of code

While developing you should set the conditional compilation constant Development = True.
This will allow you to use Outlook Object Library defined constants (olConstants) without getting compilation errors.
Once your code works, you can remove the reference to the Outlook Object Library and set Development = False.
At this point if you get compilation errors because you have added olConstants you will have to define them the way I have done above.
You can find their value by temporarily setting a reference to the Outlook Object Library again and then use the Object Browser to search for them. Click the constant and you will see its value in the bottom part of the Object Browser display.
If you have not tried to use the Object Browser before – it’s time to get started. You will love it. Just press F2 from the module editor and you are ready.

Hope it helps.

No Patrick, when you first open a form, the following events occur in this order:

Open -> Load -> Resize -> Activate -> Current

Hence, the called form is not yet the active form.

If the called form might be open already – put the code in the Load event.

Why not do it the easy way, no global needed. In the open event of the called form:

Dim strForm as String
On Error Resume Next
strForm=Screen.ActiveForm.Name
If strForm=”” Then
…….. not opened by another form
Else
…….. opened by another form
Endif

If the form can only be opened from another form you don’t need the error trapping.

It could even be done without the help of iif-stmts by using an expressing like this in the ORDER clause: Abs(Month(Date())-Month(BirthDate))

The expression will evaluate like this:

Current month	Birthday this month	Birthday next month
12	0	11
1 thru 11	0	1

One way of writing the complete SQL could be like this (using the Employees table of the Northwind sample dbs):

SELECT Employees.BirthDate, Employees.LastName
FROM Employees
WHERE Month(BirthDate)=Month([DE]) Or Month(BirthDate)=Month(DateAdd(“m”,1,[DE]))
ORDER BY Abs(Month([DE])-Month(BirthDate)), Day(BirthDate);

Replace [DE] with Date() to make it work for real.

Comment on Unicode character-encoding. By default Access uses Unicode Compression for text and Memo fields. As long as you are using entirely Latin characters (as in English, Spanish,