Search results

This link about normalization could help with the restructuring: http://msdn.microsoft.com/en-us/library/office/aa139981(v=office.10).aspx

Here is a start. This may give you some ideas. I used your names for the spotlight questions, but I suggest renaming the fields to something without spaces and special charactors. you decide.

Mihail: here is the structure. Looks like there may need to be a bit of an overhaul with normailization

Right now, there are only 1 student with a stduentID in the StudentBasicInformation table. The contactInformation table has a primary key based on the student first name are there are no student ID's in that table. The CraftInformation table has more students listed but there are no student...

WOW. there are definately some structure issues here. WHat is the point of the Naviagtion table. There is a composiet key consisting of 8 fields??!!

Looks like 2010. I can open it fine. I will look into it. what information are you trying to get?

You can utilize a rectangle and set the fill color in code based in the selection of the frame... if you do not wna tto highlight individual records. If you do want to highlight individual records, then Cronk has the right idea.

oh no.... I totally agree woth you. I would also suggest that you can utilize the TempVars collection to store the UserID og the person accessing the system and drive recordsource of the form off that userID. recordsource = SQL & where tempvars!userID = [whatevertheuserIDis]

ok. I may suggest that you change the names of those controls slightly as the other post suggested: dtUpdate and dtComplete. the word "Complete" and "Update" may be freaking out the VBA. I know that "Update" is a reserved word.

The Activity ID would not be an autoNumber field. It would be a number and it would have to allow duplicates. The Activity table may have to have a composite key of ProjectID and ActivityID. If this is just for display, then you cn concatenate the 2 keys together in a query. FullProjectID...

try to force save the record by using: Private Sub cmdReviewCompleted_Click() Me.Complete.Value = Date if me.dirty then me.dirty = false End Sub

SELECT Payments.[Contract Number], Sum(NZ(Payments.[Payment Amount],0)) AS [SumOfPayment Amount] FROM Payments GROUP BY Payments.[Contract Number];

I made an edit. Recheck the post. I forgot the "WHERE AssignTo IS NULL" :banghead:

You need to modify this for yourself, and I haven't tested, but here is a sample of my thoughts: Sub test() Dim strAvailAuditors As String Dim db As Database Dim rs1 As Recordset Dim intAvailTotal As Integer Dim strLoanAssign As String Dim intLoanTotal As Integer Dim intTop As Integer...

you may have to go a bit recursive. my theory is this: you can use a SELECT TOP 'N' where the 'N' is the number of records divided by the number of auditors. So if 5 auditors and 100 records then top 20 is selected where auditor is null or "". update the auditor and run again for the next N...

You can achieve a "feel" of this by setting the visible property to false and have a command button to unhide it: Dim strPass As String Dim strverify As String strPass = "password" strverify = InputBox("what is the password to view the tab?") If strPass <> strverify Then...

you could test the length of DioOfficeZip and append the zero... if len(DioOfficeZip)<5 then DioOfficeZip = "0" & DioOfficeZip" end if

I agree that the public function may not be needed, but It is a nice piece of code to have just in case you need it later.

Are the values in rs!email correct? did you try to view the contents of the field in the immediate window just to see if there was a typo in one of the addresses? I have lots of those :)

Public Function FirstDayInMonth(Optional dtmDate As Date = 0) As Date ' Return the first day in the specified month. If dtmDate = 0 Then ' Did the you pass in a date? If not, use ' the current date. dtmDate = Date End If FirstDayInMonth =...