Recent content by arnelgp

what the code does is Replace the form parameter criteria of the query with the actual value of Text2 on the form. after running the TransferSpreadsheet, the query is re-instated to it's original.

can you test this again, i made another module. and modify the code a bit.

you don't get error when opening these 2 queries directly from the Navigation Pane. right? and only got error when Exporting them? is the Export code from the same form, PowerBI_Export_Pop_Up_Form?

here is what I added, a Tick sound on form, frmClock6.

maybe you can show us the SQL String of those two problematic queries.

this is very fast, total re-code. i remove the module and instead, change the query string if there is parameter. see the code on the button

here again with some modifications. before running the code, Kill Excel from Task Manager(Ctrl-Shit-ESC), then find Excel. Right-click on the Excel Process, the choose End Task.

for the two problematic query, use manual export and the rest using TransferSpreadsheet. something like this on a command button. '/Code on form Private Sub cmdExport_Click() Dim strFilePath Dim arrQueries As Variant Dim i As Integer If IsDate(Me.Text2) = False Then...

for you queries with criteria (SalesInboice_Query and PurchaseOrder_Query) use manual export (the code i gave you). for the rest, export normally with DoCmd.TransferSpreadsheet.

maybe you can use a Custom export routine like on the demo. open Form1 and see code on the form and on module modExcelExport.

As I search the forum for a sample form with Analog Clock, I came across many samples. ashleedawg has some interesting demo in https://www.access-programmers.co.uk/forums/threads/making-an-analog-clock-on-an-ms-access-form-manipulating-controls-no-activex.294673/, also Markk has one on the said...

maybe what you need to start is to look for FileDialog or something. see Form1 and Module1 on this demo.

can you check this out. not related to your problem. see MainMenu form (the Auto_Date and Auto_Time textbox). I made them unbound and add timer event to set their value thus making them change the time/date in real-time.

poor AI, still to blame.

using DoCmd.Maximize, will affect all "windows" you open and will open maximized. it is better to use DoCmd.Move