Search results

Any time I see a question asking about calculating across fields, I assume the table isn’t normalized. In this case, I would have created a payment table with fields: TransactionID, [ParentID], TransactionType, TransactionDate, and TransactionAmount. There would be three records rather than...

I have seen where separate columns are added for each range so in your case there would be three extra columns with either the appropriate value or 0. Then create a stacked bar chart and set the colors as you desire.

What do you mean by “that is by default sorted by the ID field”? Are you using an ORDER BY somewhere that sorts by ID? I would never assume records will display in any reliable order without some setting or SQL order.

I’ve created un-normalized input forms to match timesheets or other forms that make the most sense and provide ease of use for employees/users. The code to load for edit or save to a normalized table is trivial. I wouldn’t make my users change their sensible paper forms or data entry screens...

I would consider using a combo box based on your table of reports and attributes. Then you could easily reference the columns of the combo box for the setting properties.

I always specify the field names in the target table in an insert statement. If Reccount = 0 Then CurrentDb.Execute ("INSERT INTO tblDNAProfile (FldA, FldB, FldC) " & _ "SELECT dnatestid, dnacategoryid, dnatypeid FROM tblDNATests"), dbFailOnError End If

Do you allow zero length strings in your fields? What is returned when you run a similar query without joining to the FarmerT? Maybe try SELECT FarmerT.RegNo, RTGST.RTGSUTR1, RTGST.RTGSMailToHO1 FROM FarmerT INNER JOIN RTGST ON FarmerT.FarmerID = RTGST.FarmerID WHERE RTGST.RTGSUTR1 & "" <> ""...

As per my previous post to troubleshoot, you should set a breakpoint to step through your code with your values like: Use the F8 key to step through the code line by line to determine where your logic is off.

I would open the debug window (press Ctrl+G) to test the functions with entered values. You can set a break point and step through the code line by line.

Can we assume you are referring to frmDocuments? You need to answer questions from those who are attempting to help you. No one here can read your mind. Your function IsTransferValid() should have a header with the design specifications.

Are you ok with running the reports by clicking a button on the 25th or do you expect these reports to be run unattended?

I think Shoebnisar is not being understood. I read the input screen would look like a spreadsheet but the data would be stored “row wise”. You can write some VBA to append as many records as have been entered into the combo boxes. It would be a basic loop through the combo boxes that I would...

This was a comment about how using the bound column to 0 as per the first three sentences in my reply. I hadn’t read this possibility in previous replies.

I believe using a column value of 0 returns the index position of the selected value. So, if the first value was selected, it would return 1. Selecting the tenth item in the list would return a value of 10. This is how Access behaved 25 years ago when a developer working for me made the mistake.

I’m not in a position to open the Access file but wonder if you considered using the running sum property of textbboxes rather than using code?

Combo boxes in forms are awesome. There really isn't a substitute with all the rich functionality.

I deleted the combo box information and changed the Display Control to Text Box. I don't get an error message. If you are still having issues, consider sharing your current file.

The issue is your lookup field (not a good idea) definition in your table design. The Row Source for [ID Unit Kerja] is set to: SELECT [Unit Kerja Peserta].[ID Unit Kerja], [Unit Kerja Peserta].[Nama Unit Kerja] FROM [Unit Kerja Peserta] ORDER BY [ID Unit Kerja], [Nama Unit Kerja]; FROM [Peserta...

First, I would check the SQL of the Row Source since this provides an opportunity for your error. Then I would delete the combo box and re-add it.

Did you try adjusting the height of the buttons and/or font? Microsoft is known for changing default fonts which can affect the rendering of forms and reports.