Search results

Okay for curiosity sake I seam to develop some ideas, how about working directly with the server before coming to the said record set instead of using link tables string I try to open the tables direct from the server. The challenge I have is that I'm not using windows directly as result I'm...

Have you considered using an ado disconnected recordset rather than caching The entire program is using DAO to switch to ADO means reprograming the codes again and chances of errors is too high, besides that I thought that ADO was replaced by DAO by Microsoft themselves.

Do you mean between 10 and 50 records? Yes and even more depending on the number of records or lines

The statement that rings a bell is "run the loop". WHAT loop? The query should bring down ALL the records you need to export, not one at a time. Access reads each row and builds the json string. Below is the result of the loop and that is what is taking too long to process! If I was to add 100...

That should already work. Is there an error message for this? Have you already tried this variant? Yes I did there are no errors at all the code works whether placed in SQL Server as a view or select query in MS Access, the problem is that its takes 5 minutes to provide the much needed data...

How many records does QryJsonPos001 typically return? About 10 and 50 zeros

Making the select statement with the joins available as an SQL server view or using a pass-through query is not an option? I used a view directly in the server, this works well but the problem comes in at VBA stage it looks like VBA does not like opening the record set from a view or PT What...

Thank you so much uncle GIZMO. We have done and followed the rules of SQL Server, example: (1) All the forms open empty including its combo boxes, the combo boxes only start building a short list when the user type in the combo box 3 matching characters (2) All queries are handled by the server...

Hi all, I'm trying to speed up the record set in MS Access being used by the VBA code below, see the code, but I got mixed up in the middle especially on the issue below by the way this is based on linked table to AZURE: (1) What happens with the concurrent users, suppose someone post a record...

But I will not give up on this one no matter what, a solution will be found soon, I had the combo boxes problem before where 3 million records are on a table but the combo box can only load 65500 record, by trying the in initialized code on the combo box now all my forms load on a maximum of 3...

Many thanks all contributors, Kindly take note that is not the live table by just a fiction table , but the point remain the same was to get a progress meter because sometimes users feel uncomfortable when a report is taking long without any response.

I'm trying to develop a progress meter to help users have an idea of how long their report or open record set is taking running, this way users will have full ideas of what is going on in the system rather than just waiting. The small, attached database has a VBA module below working in...

Thank you so much all contributors

I have come across the statement below suggesting that the memory could be very important to gain speed with MS Access linked to cloud SQL database: SQL Server is a memory hog. You'd need 32-64 gb minimum, depending on the databases it's handling. Is the above statement true????????

If you are suggesting some like below: DoCmd.OpenForm "frmCustomerInvoice", Where [InvoiceID] = 0"

Either you are doing something wrong like binding your forms to tables or queries with no criteria and using Access to filter locally. With total respect to what you are saying all my data entry form have their data entry properties set to "YES", and so they open without a single record at all...

Just filter a query either <> 0 in the query grid, I always do it that way

If you are using those codes within access and the DB or BE is access then its fine, but if you want to use the SQL server with Access then expect to pay a heavy price in terms of slowness.

Yes sir, from my own experience, using the SQL server can only be good if you are running Views for reports. But using bound forms to the table with the form's property turned to data entry still in terms of speed it is slow to about 25 seconds compared to a form bound to an MS Access table...

Many thanks cheekybuddha I will surely settle on your solution , also warm regards to all the contributors all your answers are valuable to me.