Search results

Not sure why you would do that. Because a 1 would equal 1/1/1900 if the Date field was used as the other. It keeps it cleaner if you just do like I said, and then have it as the first field in the ordering. You can then sort on the Date field with no worries. I'm not so sure you won't find...

The trigger should have absolutely no effect on Access whatsoever. Whatever is causing it is likely in Access itself.

SELECT ID, Max(four_day_peak) As [MaxOfFourDayPeak] FROM YourTableNameHere GROUP BY ID ORDER BY ID

Change the query SQL to this: SELECT tbl_idq_all.scode, tbl_idq_all.Date, tbl_idq_all.po_qty, DSum("po_qty","tbl_idq_all","[Date] < #" & [Date] & "# And scode='" & [scode] & "'")+Nz([po_qty],0) AS RunningTotal FROM tbl_idq_all ORDER BY tbl_idq_all.scode, tbl_idq_all.Date; And when I do that...

For my stuff I put the audit trail stuff in Access itself and then write it to SQL Server. But then again nobody here can write directly to the SQL Server but needs to go through Access (the audit trail I use uses ADO to insert the record in the audit trail table). But what kind of code is on...

Change your query's SQL to this: SELECT tbl_idq_all.scode, tbl_idq_all.Date, tbl_idq_all.po_qty, DSum("po_qty","tbl_idq_all","[Date] > #" & [Date] & "# And scode='" & [scode] & "'")+Nz([po_qty],0) AS RunningTotal FROM tbl_idq_all ORDER BY tbl_idq_all.scode, tbl_idq_all.Date DESC; You didn't...

All you need is an autonumber as Pat said and then you can set a multi-field index to keep duplicates out. Bob has an example of how to set up a MFI here: http://www.btabdevelopment.com/ts/mfi

Yeah, I usually just create a sort field like that in the query itself. To do so in the QBE grid it would be something like this: MySort:IIf([FieldNameHere] Is Null, 1, 0) And then set to Ascending on the sort making sure it is the first sort in the sort order.

Access doesn't calculate all when you open a report. It will calculate the page(s) it needs to immediately display but it doesn't do the others on other pages, especially for graphs. So when you scroll to it, it needs to do so. Depending on your network, your computer's memory, processor, and...

So, I rewrote it for you a bit to make it a little more efficient code (you don't need things like stDocName1, 2, 3, 4 you can just use one. Also, your ADODB creation was off and you don't need to use Create Object for objects that are being created from the Excel Object. So, look what I did...

Are the frontends corrupting or the backend? If the frontend it usually is due to a connection that drops, even for milliseconds. But if it is the backend, how big is it and has Compact and Repair been run on it lately? If not, it should be. Also, if you are getting close to the 2Gb mark it...

Can you upload a copy of the database (with fake data) so we can take a look? If you want to do so, you would need to 1. Run COMPACT AND REPAIR 2. From Windows Explorer, right click on the file and select SEND TO > COMPRESSED FOLDER. 3. Then you can upload it here (as long as the final...

Is this code in Excel then? If it is in Access and they don't have Access installed, it isn't going to matter if you have early or late binding in that case because they won't be able to run anything from Access anyway.

Oops, forgot we weren't in VBA (Me in VBA refers to the current class object, which would be the report). Just change it to use WHERE CharacterizationReportQuery.temperature = [temperature] instead

You can do it quickly by using a reg file. Save this as a .reg file and then just run it on each pc: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Access\Security\Trusted Locations\Location0] "Path"="C:\\YourFolderHere\\"...

You have to deal with NULLS. Surround each of those with the NZ function like this: Nz([Att1Pt],0) + Nz([Att2Pt],0)...etc. And that calculation makes me think you don't have a properly normalized database.

TRANSFORM Sum(CharacterizationReportQuery.Fails) AS SumOfFails Assuming that the field is in that query and assuming that your report group is by temperature SELECT CharacterizationReportQuery.VDD FROM CharacterizationReportQuery WHERE CharacterizationReportQuery.temperature = Me!temperature...

I have tried everything I can (Access 2007) to get the mouse wheel to do anything while in a form. It won't unless you add code to the On Mouse Wheel event. So, any corruption isn't likely coming from that but is something else.

You are using it to get multi-valued field values, are you not? It isn't just for anything. Can you explain more about what it is you are doing? EDIT: Oh, and you are using this in an ACCDB file, correct?

In 2007 and 2010, there is an event for the scroll wheel which can be either used or ignored. If you are using an add-in to enable scroll wheel stuff, I would suggest removing that and then modifying your form's scroll wheel event to do what you want it to do.