John,
I created table importing data from As400 using ODBC I series . I notice now that almost all numeric fields were imported as Decimal fields very often with precision 28. In reality the data inside these fields can be integer or long integer (like the fields that indicate the year or the week for example).
I used the table like they were imported and in addition, when I read and process the data using vba, I did not declare correctly all variables …leaving Accees to manage them .
What I will try now is convert decimal fields in integer fields and I will declare the variables in correct way in order to optimize the use of the memory
If after this still I have the problem, I will post the code
Could be that at the end, back to this problem, there is my bad programming that do not come out in 32 machine but come out with 64 Bit machine that run software 32 bit
Thank you
Valentino
Valentino-
The two 64 bit machines should be faster.You would need to post a copy of your code to see if we can spot any problems that would be slowing it down.John Viescas, AuthorMicrosoft Access 2010 Inside OutMicrosoft Access 2007 Inside OutMicrosoft Access 2003 Inside OutBuilding Microsoft Access ApplicationsSQL Queries for Mere Mortals(Paris, France)
On May 31, 2014, at 4:46 PM, Valentino Avvisati valentino.avvisati@gmail.com [MS_Access_Professionals] <MS_Access_Professionals@yahoogroups.com> wrote:Hello John-Thank you for the answerI'm not really an expert but an "heavy" user of Access that is learning by doing, from this group and your books …I used my laptop (windows 7 32 bit when I built the application ) and windows XP where I run some scheduled process that produce some reportIn both where ok,
After I moved the application to two machine 64 bit:One is virtual machine with Intel xeon CPU E5620 2.40GHZRam 2 GB (effectively not too much)The other was a Real machine with windows 7 64 bit intel core I7 3,30 GHz8 Gb ram, much more powerful of the machine where I do not have issue that is anWindows Xp Dell AMD Athlon 64 x dual Core processor 4200+2,20 GHz 33 GB ram
Mainly the procedure make d Do loop cycle on a table to take one key code after I use this code to create query using db.CreateQueryDefThe procedure create open and close many time a queryIt look like this is very slow in 64 bit environment it is very slowIt is also true that I did not declare all variable, I'm not an expert and probably I also made some mistake that decrease the performance and use a lot of resources, but up to this moment I did not have any problem and I do not have problem in 32 bit.
2014-05-31 9:02 GMT+02:00 John Viescas JohnV@msn.com [MS_Access_Professionals] <MS_Access_Professionals@yahoogroups.com>:
Valentino-
When you run a 32-bit application on 64-bit Windows, there's extra overhead having to "thunk" all the 32-bit address to actual 64-bit and back, but it shouldn't be that noticeable. What are the other characteristics of the two machines? How much memory on each? How fast is the processor? Access is particularly sensitive - especially when running complex queries - to the amount of memory available. In earlier environments (Win 98), you could often double the speed of Access simply by adding more memory.John Viescas, AuthorMicrosoft Access 2010 Inside OutMicrosoft Access 2007 Inside OutMicrosoft Access 2003 Inside OutBuilding Microsoft Access ApplicationsSQL Queries for Mere Mortals(Paris, France)
On May 31, 2014, at 8:28 AM, 'valentino avvisati' valentino.avvisati@gmail.com [MS_Access_Professionals] <MS_Access_Professionals@yahoogroups.com> wrote:Good morning,
I have built an application in microsoft access 2007 that is doing some elaboration (repetitive query and successive elaboration on data extracted)
The database is divided I two file, (the second file just stock some tables ad Is located in same directory of main file mainly because , during the elaboration, the file increase very fast ii dimension)
The procedure run In around 30 minutes in windows xp 32 bit environment and also under windows 7 32 bit. This is ok for me.
the same file moved to windows 8.1 office 2013 (or also windows 7) but 64 bit machine , take so long time that I always stop before end (4-5 time more)
I'm not sure if the problem is really the 32 bit environment or due to the fact that I do not follow all the rules to be efficient, but it look like is appearing only when I move to 64 bit machine
Somebody knows why this occur and possible solution?
Thank you to all (really very useful group)
Valentino Avvisati
Posted by: Valentino Avvisati <valentino.avvisati@gmail.com>
Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (5) |
Tidak ada komentar:
Posting Komentar