Search results

Okay, figured it out. I had to go into the Chart Settings and select my Axis category, then choose "Day" since it's a date field. Thanks for the assistance!

So I have the query part fixed, but when I try and modify the "Transformed Row Source" value to edit the SQL query, it won't let me save. Shows this (which I confirmed none of those reasons to be true):

I can try that, but if I wanted to keep days that are actually zero, I could limit to items that are not null right?

I have a bar chart I'm trying to setup using historical data from a table. I'm tracking the data by date, and the table column being charted on the axis is set as a Date/Time field. The issue is that my recorded dates are spread out, not daily. So the chart is displaying all the dates in between...

I have the following code: tblName = "TableA" fldName = "User ID" sqlStr = "SELECT " & fldName & " FROM " & tblName & " WHERE '" & fldName & "' = '" & rs1.fields("Username") & "'" Set rs1 = currentdb.openrecordset(sqlStr) It runs fine when fldName doesn't include a space (ex: UserID), but I...

@Gasman - yes, the first time through the function, the copyfromrecordset dumps the data into excel correctly. Stepping through a little more carefully, it looks like it has some kind of issue with the .listobjects.add portion from the 2nd run and on. I'm trying to look at why it doesn't like that.

Got it. I'll go double check to be sure.

I did not. All the variables/objects were assigned appropriately.

I have. It hits that copyfromrecordset line, then on the next step just goes back to the main function. I've never seen it behave like this before, not without an error along with it.

I have the following code that is included in a function that runs through a recordset of users. It executes perfectly for the first record. When it gets to the second record, the code runs the ".Range("A2").CopyFromRecordset rs1" then skips back to the main function and doesn't finish out the...

This article led me to the solution. I was right, the double quotes were a problem. https://stackoverflow.com/questions/13123230/writing-formula-into-excel-through-access-vba

I have the following formula that runs as expected when used directly in Excel. But when I try to add it into my Access VBA, I get error 1004 "Application Defined or Object Defined Error". I think it has to do with my double-quotes to identify text in the formula, but I don't know how to...

StrID, it has a problem with something in the split, but I couldn’t figure out why

I don’t have it in front of me, but it was basically: dim strID() as string, rs1 as dao.recordset StrID = split(“” & rs1.fields(“userid”) & “”), “;”) where rs1 is how I’m pulling the userids from the table

So I did try using split earlier but I kept getting an error type mismatch, I think because of trying to pass a string variable into the split function expression. Unfortunately, I can’t store the data differently due to how the entire process is managed (which I can’t get into for proprietary...

I have a table of users where, for application reasons, IDs are stored as "user123;user456". I also have a table of their records to store their status from Active Directory. How can I go about splitting that string up at each instance of a semi-colon, then compare that user ID with the status...

Considering I’m self taught, I’m excited (and terrified) to say that actually made sense! I’ll give it a shot when I get back to my PC tonight and provide an update. Thanks Doc_Man!

I’m posting from my phone so I don’t have code on me at the moment, but here’s the situation. I have a form that contains two sub forms, two combo boxes, and a text box. Combo box A selects an application, which after update will populate sub form A with data (displayed in database view)...

Sorry for being late to the game, but thank you to everyone who responded. The above solution did exactly what I was looking for.

The syntax is correct, but Access is producing that error on the formula when I try to run it. The only difference between the pic and Access is having an extra set of double quotes around ";" in order to define it as a string when the formula gets passed into Excel