Search results

Thanks for the quick response, not exactly was I was hoping to hear, but it is what it is. Looks like I need to contact IT.

I have had some reports within our company that switching to the "New Outlook" is breaking some of the VBA code I have written for our Access App. Specifically I have some code that generates and sends an email through Outlook that we have been using for years with no issue, lately I have been...

Originally in the example code the data type was set to Long, which gave me a "0" for both the min and max, essentially making the axis disappear. I haven't used numbers this small in a chart before so it did bring up some challenges, but as soon as I changed the data type everything started...

Thank You The data type single works just fine. I think we can call this a wrap, here's what I ended up with compared to my first snip.

Thanks for the feedback I believe I am making some progress, I discovered that left on it's own Access seems to always start the axis range @ 0 for decimals less than 1. When I debugged the example code I was getting 0 and 0 as the min and max values for the axis. I ended up having to change...

Ya I don't know if it is the version of Access that we have but I read through those and even tried some of the examples. The examples work fine when run, but fail when I try to replicate them in our live version.

I have been scouring the threads but nothing seems to fix my issue with the primary axis. I have tried setting the min and max manually but the same chart is used for several product models and the range is different between models. I have tried using vba, but setting the min and max that way...

I am currently looking for the same solution, this one looks good but I get a run-time error '438' Set objChart = Chart463.Object Object doesn't support this property or method

I'm having a bit of trouble with my code: Dim strModel As String Dim strDateCode As String Dim strMsg As String Dim nValue As Variant Dim nQuantity As Variant Dim i As Integer If IsNull(Me.DateCode) Or IsNull(Me.ModelNumber) Or IsNull(Me.Quantity) Then...

I finally managed to get my hands on the laptop this morning, I was able to verify that the application was behaving differently. As previously pointed out the network although causing a delay, wasn't interfering with the form event. I don't know the exact cause of the problem, but I was able...

It is a very simple piece of code, the user makes a selection from a combo box, as long as something is selected a message box comes up with a Yes / No option for the user. It is on the "after update" of the combo box.

It is definitely split, however I am relying on them to download and install locally, I need to check that for sure.

It's nothing very complicated. The user makes a selection from a combo box, if for some reason they don't select anything then the code is not supposed to execute. Otherwise a message box is supposed to popup offering a Yes / No selection. Like I said it works fine on my desktop but I am...

I should have time tomorrow to dig a bit deeper, they have been using that workstation before but that does bring up a good point. We typically upload the file to sharepoint and have them download it locally, I should check to see where they are running it from.

The event triggers a Yes/No message box, and the code executes based on the user selection. During my demonstration there was no popup message, and I was told there wasn't one on the production floor. I still have to go down and confirm it, and i know that the wireless connection is a bit flaky...

I have noticed lately that I am getting differences in the way the vba code is behaving when run from various network computers. For example, a couple of weeks ago I introduced a new data entry form for our production group. The form and code worked as expected when I tested it at my...

Thanks Colin, I realized later that it was probably because I was messing with the size of the main window. Some users were experiencing reports opening minimized to the task bar. What I ended up doing was changing the Report settings to: Auto Resize No It works but you have to change every...

The only issue that I have with "Maximize" is that it opens the window to the size of my screen, not the size of the report. Is there a simple way to get the window to match the page size?

It doesn't seem to matter what size they are when they are closed, they still open tiny. It also seems to only affect reports opened via command button, if you double click the report directly it opens normally. This just started doing this recently could it be related to any Office 365 updates?

Recently my reports have started opening as very small windows. I haven't been able to determine why. The VBA code: DoCmd.OpenReport "rptPrintFATDataS8500", acViewPreview, , "[SystemNumber] Like '" & strSystem & "'" I tried adding ",acWindowNormal" to the end but it does not seem to make a...