Search results

Change your SQL to this and try: SELECT tbl_idq_all.scode, Format([Date],"mm\/dd\/yyyy") AS poDate, 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...

No, it isn't right. You left in something that shouldn't be there and you can not use the extra & "'" & as you can see in the corrected version below. Set rst = dbs.OpenRecordset("SELECT CLASSNO, CUSTNO, FULLNAME, EMAIL, REGID " _ & "FROM MCTEST2 " _ & "WHERE CUSTNO=" & rstInsert![CUSTNO] & "...

You obviously do not understand how GUIDs are created and so I will stop trying to get you to see that they are completely safe for you to use. You seem to think that using your method, nothing can go wrong. Well, I hate to break the news to you - ANYTHING CAN BREAK OR GO WRONG. The odds of...

Is regionID really text (which is the way you are saying it is in your code because you have quotes around it) or is it a number? If a number then this part " AND REGID=" & "'" & rstInsert![REGID] & "'") would be: " AND REGID=" & rstInsert![REGID] ) without the quotes and that would...

This: oRst.CursorLocation = oRst.adUseClient should be oRst.CursorLocation = 3 If using late binding or you can set your own constant Const adUseClient As Integer = 3 Also, again I will state - you don't even seem to be using the recordset so why open it?

Is your main form being displayed in single record format or continuous or datasheet view?

I don't think it is that issue. Are you somewhere where the dates use the dd/mm/yyyy format instead of the US format? Here's what I see when I run your query.

Sounds like a bit of corruption occurred or the VBA got out of synch. That can happen at times and a DECOMPILE and then Compile again can help.

Instead of using it in the table just use it like this: Order status: DateDiff("d",Date(), [Due Date])

I understand that. And I can't tell why it would do that for you like it is but I can tell you that you are playing with fire if you do not do like I said. Read the article I posted because there are very valid reasons why you need to do this. It has nothing to do with using a macro or vba...

I would suggest to not use a parameter prompt but instead use a form for input. It will be more efficient and less annoying to the user should they type something incorrectly and they hit enter at which time they would realize that they need to run it again and then type what they need again...

Split the database to a backend and frontend and give each user their own copy of the frontend. That is the best way for multiple users and to avoid issues like this. This article would be a good one for you to read as it goes into why splitting is essential, not just a choice...

It is ALWAYS best to let each user have their own copy of the frontend. It is even best to split when it is a single user. It helps avoid corruption and reduces the chance of losing the entire thing.

You are incorrect. You most certainly can and it is when the Autonumber is set to be ReplicationID. There is a one in 2^128 chance of a duplcate. You could have one billion people input one billion records a year for 10 to 20 years and still not likely get a duplicate.

That is the RecordSelector and you can set that to NO in the form's properties.

Best to avoid the DoCmd type commands at times because Access doesn't always know which item you want to use with it. I would use the filter explicitly: Forms!FormNameHere.Filter = "xxxxx" Forms!FormNameHere.FilterOn = True

1. I reformatted it for you. 2. You need brackets around NAME (you did in the recordset callout of it but not in the SQL part because NAME is an Access Reserved Word). 3. If the data is not text, but number you don't include quotes. I used CHR(34) to simplify it. 4. With such a long string it...

The code I gave just takes you to the record. If the form is set to allow edits and your underlying record source for the form is updatable, it would be editable.

Dim rst Object Set rst = Me.RecordsetClone rst.FindFirst "[FieldNameHere]=" & CriteriaValueHere If rst.NoMatch Then Msgbox "Record Not Found" Else Me.Bookmark = rst.Bookmark End If rst.Close Set rst = Nothing

Are all of the graphs visible at the same time or are some only showing as you scroll down the page (I'm guessing that is correct). Which then it also would fit into what I said. And, perhaps you are trying to show too much on one page.