Search results

I have no experience with working with unnormalized databases except that they are usually a complete hassle. With that many records you might be better off using a higher end back-end database system than Access, which can handle that many records. And using an access frontend. Maybe someone...

I am not completely sure, I believe it depends on your structure. But I don't believe each client should have their own data table, otherwise you'd have 1M tables. (Since to have 1M records in a truly normalized DB, there would technically be 1M "users" if I understand your request correctly)...

Telling your Girlfriend/Wife (Whom has the same degree as you) that her database design is incorrect and won't work!

If that 1M records is over a long period of time, I would recommend splitting older records off into a separate table/backend for archiving. And if someone needs to see all of the records you can use UNION queries to combine them together again.

To get the one not currently being entered, try something like: "[Family Name] ='" & Me.Family_Name.Value & "' AND [Given Name]='" & Me.Given_Name.Value & "' AND Not [Job Number] =" & Me.Job_Number.Value This should automatically look for the highest job number, but if not there may be a way...

Change #02/10/1974# to [Enter a Date] and it will prompt the user to enter a date for the query. For example: Expr1: IIf((DateDiff("w",Date(),DateAdd("yyyy",(DateDiff( "yyyy",[Enter a Date],Date())+1),[Enter a Date])))>52,(DateDiff("w",Date(),DateAdd("yyyy",(D ateDiff("yyyy",[Enter a...

Excellent, glad you got it working. :)

Try making a button beside the e-mail address field that says "E-mail this user" with the following code: FollowHyperLink "mailto:" & me.emailfield As long as a default email client is setup, this should work.

If IsNull(Me!Name) Or IsNull(Me.CID_) Or IsNull(Me!Date) Or IsNull(Me.Intake_Staff) Or IsNull(Me.Location_Code) Or IsNull(Me.Office_Code) Then DoCmd.RunMacro "required_fields" Else DoCmd.Close End If EDIT: Code fixed, good catch :)

You actually technically did your math wrong. One in ten people, have an out of body experience during their life. Technically you are right that if the current planet has 6.5 billion people, we would see 650 million OBE's during the entire lifespan of that 6.5 billion, which is roughly 650...

Ok I will explain a bit more clearly what each one does. The DLookup looks up the primary key (PersonID in my example, just because this is the easiest field to pick if something exists or not), from the table where you want to lookup the duplicates (tblPersons in my example, this is the table...

Actually, instead of that jumble just use two fields inside your query. The first field has that Exp1 that returns the 19, Then field 2 is: Exp2: IIF([Exp1] > 12, [Exp1] - 12, [Exp1]) This should be much shorter.

Ok, I found out it was an issue between our regional settings, when I changed 02-10 to 10-02, I also get 19 months. It happens because of my code apparently doesn't properly check if the birthday has passed this year or not. I guess my temperary fix would be to use an IIF statement to see if...

When I run that exact line I get 11 Months. I believe the problem is in symantecs, as you see I accidentally inputted the date two different ways... on my machine this works, however because of your regional settings this may be causing a confusion. I believe it's reading the first date as...

Expr1: DateDiff("m",Date(),DateAdd("yyyy",( DateDiff("yyyy",#1974-02-10#,Date())+1),#02/10/1974#)) The middle part finds the next birthday by taking Todays Date minus Birthdate in years... then adds that many years + 1 to the year because this will be the next birthday. Then it compares the...

Not sure if I understand entirely. If you have the query already built, you can use a DLookup: =DLookup("[AddressLine]","qryAddress","[PersonID]=" & PersonField If you don't have the query built, and want it displayed on the form, you would enter something like: =[FirstName] & ", " &...

I believe you can still use DLookup to see if a value exists. If DLookup("[PersonID]","tblPersons", "[LastName] ='" & txtLastName & "' AND [FirstName]='" & txtFirstName & "'") > 0 then msgbox "It Exists" End if You can also use recordset. dim db as DAO.Database dim rs as DAO.Recordset dim...

If you want each user to open a different form, you can create a field in the Users table called "UserForm", which stores the name of the form they wish to use. Then on the Login Code, once the user validates you can set the open form variable to be that of the form stored in the table. For...

Oh yes, great idea, and one more thing... If InStr(fullText, "<image>") > 0 then fullText = Left(fullText, InStr(fullText, "<image>")) & "<Image Removed>" & Right(fullText, Len(fullText) - InStr(fullText, "</image>") + 8) End If

Unfortunately Microsoft neglected this feature, maybe Access 2007 AE has it however. We'll have to write some VBA code behind the scenes much like checking the textfields. 'If the sentence is shorter than 30 characters, and contains a comma, then remove the comma. If InStr(fullText, ".") <= 30...