Search results

Search the forum on the word "clock". This has been answered numerous times before. --Timing Mac

First Aid Ok, there's a couple of things you need to do. This IS a sorting/grouping problem (but stemming from the query), coupled with a design problem. The basic solution to your problem is that your underlying query should only have ONE project id field, whereas you brought in one for each...

You went to the Sorting/Grouping dialogue, selected PROJ_ID as the grouping field, checked that Sort Asceding was turned on (default), and that Group By was set to "Each Value" (default), and Access gave you something other than your details grouped by Project ID? Ummm... Are you sure? If...

Sounds like you want to group on ProjectID. Check out the sorting/grouping options available in the report's design view. --Group-By Mac

This "problem" is solved for you if you use the wizard, and has been answered many times over in these forums, not to mention in Access Help and the Northwinds sample. Northwinds is probably the quickest resource, you can just copy what's there. --RTFMac

If you hit a snag, just shout out. Also, keep checking this post, as one of the many wiser folks may give you better guidance. --Not-Actually-Senior Mac

Sounds like you're going to need lots of junction tables... tblSessionTypes autoSessionTypeKey (PK) txtSessionTypeName tblSessions autoSessionKey (PK) dtmSessionDateTime fkSessionTypeID - (1:M from tblSessionTypes.autoSessionTypeKey) tblTasks autoTaskKey (PK) txtTaskName...

I live in NYC, couldn't POSSIBLY add anything in terms of knowledge that you don't already have, but would be happy to help in any way I could. Proofreader, feedback, guinea pig, whatever you need... In terms of an approach, I haven't read that many Access books, but then I haven't READ that...

PAT: How's that book coming, BTW? I've been looking forward to it for ever so long... --Anxious Mac

Andy: You could probably help Neil help you if you would post some example of the report you have and tell us how it differs from the report you want. A screenshot would do, a zipped version of the .mdb would be even more helpful. --Sample Mac

I think the "goto" methods are strictly for navigation. So, go to the new record as above, THEN populate the controls, then save the record. Personally, I would build an SQL statement to add the record and use the DoCmd.RunSQL method instead: dim strSQL as String ... then, in the for loop ...

pas: It looks like you might need to back up a step and normalize your tables. Right off the bat, you're storing the same info at least twice by having duplicate [Drawing Title] fields. Once your tables are in good shape it will be easier to accomplish everything else. --Normal Mac

Since the two that don't check for IsNull do work and the two that do check don't... I'd reiterate the suggestion of setting a default value of 0 for avgloan before the select statement. Keep in mind that Access treats 0 values, blanks, and Nulls differently. Checking IsNull is not the same as...

Re: Still not working In spite of Intel's marketing, nothing happens at the same time in computers. If you want two things to happen on one event and want to keep the in separate routines, create a third routine that calls the other two and assign that to the On[whatever] event. One glitch...

Well, poop. Time to start grasping at straws: Check the fields in your table design, make sure they are set to the types you are calling for. Open up the VBA and try building that query in a string variable before you get to the open statement. Put a watch on the string variable and step...

May need # signs to let Access know that this is formatted date info? Try: Set rstUserName = dbscurrent.OpenRecordset("select * from [tbl User] where [User Name] = '" & strLogonUser & "' and [Logged In] = '#" & strLogonTime & "#'")

You said they were joined by the PK, but what type of join is it? It sounds like you're going to want to use a junction table between the two, so that you have maximum flexibility in changing things on either side. Search the forums and Access help for the word junction, you'll probably find...

Search Access help and these forums for info on the OnTimer property: --RTFMac

Try: SELECT DISTINCTROW [companyGraphData].[Dept], Sum([companyGraphData].[TotalRep]) AS [Sum Of Rep], Sum([companyGraphData].[TruckCount]) AS Trucks, (Sum([companyGraphData].[TotalRep]) / Sum([companyGraphData].[TruckCount])) AS [AvgPerTruck] FROM companyGraphData GROUP BY...

Got it--my mental lapse was in not envisioning a three-way juntion table. Charges & details junction I got, but not the best way to relate both to a single defendant (alternately, defendant & charge I got, but not the best way to factor in detail...) Actually, won't there also need to be a...