Search results

Well I just finished switching all my Access queries into Mysql views and the difference is amazing. Running just a basic speed test that opens my query 'Inventory_qry' and moves though all the records, I got 12 seconds using access and less than 1 second using Mysql. The best part was that I...

The frontend of the database is written in access 2007 with the backend being mysql 5.1. This database is for the fabrication portion of a manufacturing plant. Basically the foremen order the parts they need to build equipment using the Orders_tbl and Orders_detail_tbl. Those parts are then...

lol no problem. The structure is fairly consistent all the way though but let me know if you have any questions.

Below is a description of my tables and columns. I wasn't sure what all info you needed so let me know if I have forgotten anything. I also attached a text file with the same information for easier reading.

No I knew what you meant :). I am not faint of heart but before anything in production changes it will be changed on my test server to see if it is worth it or not. I will write up what each table is for on monday and post it if you are interested in understanding how I put it together. I am...

The database is in production but I keep a test server running a duplicate so I can work on improving it without risking the data.

I am open to suggestions.

That is what I was afraid of. When I filter that recordset it is still quite slow. You can try it and see what you think. On the "Inventory_frm" there is a box at the bottom to filter by description. I am going to keep going with converting all the queries to mysql views to reduce constantly...

After a little research this morning I have realized I can't run a pass though query because my "Inventory_qry" is based of several other queries. I think I am going to have to look into running things though views in mysql. Does anybody have any experience with views? I am wondering how many...

i I will think about if i have to pull all the records at loa but first i will try the pass through query. and yes all the tables have proper indexes and relationships in mysql.

No problem.

@Beetle It is 'Inventory_frm' that is the troublemaker. @GinaWhipp The tables don't matter. In production all the tables are in a mysql database.

I have reattached my database as a mdb file. Let me know what you think.

Yeah I can do that. It will be tomorrow before I can convert it as I don't run access at home.

It is only my main form that is a troublemaker. It is read only but it pulls data from several tables though several querries to get the end result with is a list of my inventory as calculated by the data entered. It might be the the query is just too complex. I am not sure of a way to simplify...

Maybe I didn't make it clear in my initial post. The database portion is actualy handled by a mysql server so I don't think I need worry too much about corruption but just the same I run a daily backup through a cron job. Getting the data seems to run fast enough it is the querries that are...

The tips on those sites were not very helpful unfortunately. I think that the main problem might just be network speed. When I use the database on my system which is connected to the server through 1 switch, it is acceptably fast. (It probably takes 15-30 seconds to load my main form). However...

Thanks for the links. I have read quite a few things on improving database speed but I will look specificly at these and see what they have to say.

I developed the attached database to track parts at my work. It has been rewritten with new features a few times but it just keeps getting slower and slower to use. I was hoping someone would take a look at it and tell me if it is just beyond the scope of access or if there is something that...

VilaRestal I looked over the code you rewrote for me and it does look much simpler than what I wrote so thank you for that. I did get my code all working and I have actually taken out a lot of the extra stuff you mentioned. I am going to keep these methods in mind the next time I need to...