Replies

Rich,
Thanks for the followup.
The pc’s are not sharing the same application. The mde is on the local workstation and is linked to the tables in the mdb backend.

For testing purposes, I even put the front end and back into one, with the same results. My next step is to look at code behind the form, though I am not sure at this point what I should be seeking.

Thanks.

kwvh

Thanks Wendell,

The DateDiff() does give me the difference but does not give me years and months, at least not that I can find.

I am seeking the value to include in a report. The report contains several individuals with some demographic information. Included in the needed information is the the length of time in years and months that the employee has worked for the company. I found some nice snippets of code in the thread 187447, but I don’t know if that will do what I need, nor how to incorporate the function into fields on a report.

Sorry to be so ignorant, but I am trying to learn.

TIA

Ken

Well, on the other hand, I may be in Santa Clara (Paramount’s Great America) on business. Who knows, I may get there before you get to TX. Regardless, I thank you very much!

Kwvh

God Bless You! I owe you a lunch.

Thanks Pat and WTH. I can see this is going to involve some work. I am glad is not one of the many allergies that I have.

Ok I will try this. However, I notice I did not indicate in initial post that all the reports are based on queries. Will this have any effect? Of special significance is what if the criteria in the filter includes a field NOT in the report query.

For example, if I have filtered the data set, via form, for:
Date, department, and employeename

AND the report the user wants to print doesn’t contain the “employeename” in the report query, will it still run the report?

Thx.

John asked for my “solution”. Obviously I didn’t do a very good job explaining it. LOL

The Opportunity:
My customer(s), like me, are over 40 and therefore “age related visually challenged”. In addition, the resolution of their monitors are not the best in the world. With a good monitor and good eyes, it is not difficult to see which tab is on top, but they have neither great monitor nor good eyes.

The properties of the labels on the form are set so they change colors when the user is in a field/control. This makes it very easy for the user to determine what field the cursor resides in. This was probably my undoing, as they really like that feature and it works very well in 97. (can’t use it in Access 2k due to screen flash issue that Mark mentions).

Because it is easy to tell which FIELD they are in, they want be able to tell at a glance what TAB they are on.
[For the life of me I don’t know why. If they know what field, what difference does it make what tab? But that is another issue. I am here to serve.]

The Solution: (Remember, I did say it was low tech)
I put a wide (five point) red horizontal line beneath the text on each of the tabs.

The forms have a gray background with little or no color on the controls or labels. As they tab through the pages, it is immediately obvious which is the current tab as there is a bright red line at the top “underling” the text on the tab indicating the “active” tab.

The Results:
Emailed sample to customer to review, and set up appt for Monday to meet and discuss. Got email back this morning that is exactly what they wanted. So Monday, there is no need to meet, just install. kewl! Sometimes I have a tendency to make things more complicated than necessary.

Thanks for ALL the help so many have given me these last weeks. This is a great community of folks.

Ken

Check settings in the Tools>Options>Tables/Queries>”AutoIndex on Import/Create”.
Anything listed there will automatically create indexes upon importing.

Kwvh

Thanks Wendell,

I found a “low tech” solution that looks promising. A five point red line beneath the text on the tab. Seems to meet the need. I will show them on Monday and see if I can get their blessing.

Kwvh

Mark,

Thanks again for your solution. It works great! That is a super control you have that allows switching of the fly. I never considered that. Tunnel vision I suppose.

Ken

Thank you! It worked PERFECTLY!

This is a snippet of code that I use for converting to Proper. I didn’t write the code, I downloaded it a long time ago from http://www.mvps.org. Dev Ashish posted it, though his name was not in the documented code. I hope this helps.

‘******************* Code Begin ****************
Function Proper(X)
‘ Capitalize first letter of every word in a field.
‘ Use in an event procedure in AfterUpdate of control;
‘ for example, [Last Name] = Proper([Last Name]).
‘ Names such as O’Brien and Wilson-Smythe are properly capitalized,
‘ but MacDonald is changed to Macdonald, and van Buren to Van Buren.
‘ Note: For this function to work correctly, you must specify
‘ Option Compare Database in the Declarations section of this module.
Dim Temp$, C$, OldC$, i As Integer
If IsNull(X) Then
Exit Function
Else
Temp$ = CStr(LCase(X))
‘ Initialize OldC$ to a single space because first
‘ letter needs to be capitalized but has no preceding letter.
OldC$ = ” ”
For i = 1 To Len(Temp$)
C$ = Mid$(Temp$, i, 1)
If C$ >= “a” And C$ <= "z" And _
(OldC$ “z”) Then
Mid$(Temp$, i, 1) = UCase$(C$)
End If
OldC$ = C$
Next i
Proper = Temp$
End If
End Function
‘******************* Code End ****************

Ken