+- MetalworkingFun Forum (http://www.metalworkingfun.com)
+-- Forum: Machining (http://www.metalworkingfun.com/forum-5.html)
+--- Forum: General Metalworking Discussion (http://www.metalworkingfun.com/forum-6.html)
+--- Thread: Tool Log - Database (/thread-100.html)
RE: Tool Log - Database - Mayhem - 01-09-2013
(01-09-2013, 11:13 AM)EdK Wrote: Darren,
Any update on this?
Thanks,
Ed
Unfortunately not Ed. The code requires a complete overhaul to enable it to run on a 64 bit system and I simply don't have the time to do that just now. I was hoping that the fix would be a simple one, as my VB script knowledge is limited and I had a lot of help in piecing together the database.
In fact, a number of the key functions that took my time intensive (and very basic) database into the more streamlined version it is today is because of the generosity of others who helped by contributing code. The search engine that is extremely powerful and something that I utilize very often was written by someone else.
I will endeavour to try and find someone to help with the recode and will update this thread and the front end of the database if this happens.
RE: Tool Log - Database - ml_woy - 01-09-2013
(03-04-2012, 07:49 AM)Mayhem Wrote: Tom - this is one of the reasons I decided to share it. It actually didn't occur to me that anyone else would be interested in it until I read a post elsewhere that a number of people were concerned that their wives or children would be burdened, or ripped off should they inherit their tools and equipment. I was actually surprised to see it has been the most downloaded file on that particular site.
You are right, I have thought about that a lot. Having inherited my grandfathers, fathers and many other deceased friends tools, I want to make sure that when I pass they either go to a worthy home or are sold for a reasonable price. I know my kids and son in law have no interest in my tools.
RE: Tool Log - Database - EdK - 01-10-2013
(01-09-2013, 08:48 PM)Mayhem Wrote:(01-09-2013, 11:13 AM)EdK Wrote: Darren,
Any update on this?
Thanks,
Ed
Unfortunately not Ed. The code requires a complete overhaul to enable it to run on a 64 bit system and I simply don't have the time to do that just now. I was hoping that the fix would be a simple one, as my VB script knowledge is limited and I had a lot of help in piecing together the database.
In fact, a number of the key functions that took my time intensive (and very basic) database into the more streamlined version it is today is because of the generosity of others who helped by contributing code. The search engine that is extremely powerful and something that I utilize very often was written by someone else.
I will endeavour to try and find someone to help with the recode and will update this thread and the front end of the database if this happens.
Darren,
Is the code available for downloading? I haven't done much with databases but did take a couple of semesters of VB in college. I wouldn't mind taking a crack at it.
Ed
RE: Tool Log - Database - Mayhem - 01-10-2013
Ed,
All the code that controls the database is in the front end (C:/Tool Log/Data/Tool Log.mdb).
There appear to be specific changes from VBA6 to VBA7 as used on 64-bit systems. However, some of what I read appears to suggest that there should be forward compatibility, which clearly isn't the case here.
These are the two sources that I was pointed to:
http://msdn.microsoft.com/en-us/library/ee691831.aspx
http://support.microsoft.com/kb/983043
I had meant to ask Tony Wells about this, as I believe he has friends who are knowledgeable on Access. This has reminded me to do that...
RE: Tool Log - Database - Mayhem - 11-24-2013
OK - I think the issue has been resolved and I have uploaded a new file in the resources section (CLICK HERE).
I don't have a 64 bit system but the person who did the coding sent me a screen shot of it running on his 64 bit system. Ed - are you able to test it out please?
RE: Tool Log - Database - EdK - 11-24-2013
(11-24-2013, 06:13 AM)Mayhem Wrote: OK - I think the issue has been resolved and I have uploaded a new file in the resources section (CLICK HERE).
I don't have a 64 bit system but the person who did the coding sent me a screen shot of it running on his 64 bit system. Ed - are you able to test it out please?
Darren,
What timing. I've been thinking about that database lately. I'll test it out and let you know how it goes.
Thanks,
Ed
RE: Tool Log - Database - Sunset Machine - 11-24-2013
Wahh! Still won't open in Openoffice (http://libreoffice.org). I'm not even sure what bits I'm using -- I think 64 is for 4 gigs of ram on up. I only have 1 gig, so 32 bits? Kexi (http://www.calligra-suite.org/kexi) thinks it's a JET Database. Huh? I only have one JET tool, a bandsaw.
F.R.E.D
I forget what the F stands for, but the rest is Ridiculous Electronic Device.
RE: Tool Log - Database - EdK - 11-24-2013
The amount of memory your computer has installed has nothing to do with it being 64 or 32 bits. The 64 & 32 bits refer to your operating system and your processor. You can't run a 64 bit program on a computer with a 32 bit processor or operating system. You can run a 32 bit program on a computer with a 64 bit processor and operating system.
Ed
RE: Tool Log - Database - Sunset Machine - 11-24-2013
Here's what it says. Seems to be RAM related, but I can't make heads or tails of this stuff anymore. Linux, btw, but I don't see why it would matter.
no memory segmentation into low and high memory
up to 128TiB virtual address space per process (instead of 2GiB)
64TiB physical memory support instead of 4GiB (or 64GiB with the PAE extension)
16 general purpose registers in the CPU instead of 8
I found the store receipt: "AMD Athlon 64 Dual-Core 4400+". That looks like it might be a 64-bit processor.
I seem to remember the recommendation was to run 32-bit unless you had need for lots of RAM. If you ran 64-bits on low memory machines, it would run slower. I could be completely mistaken, but fairly certain most people go 64-bit only because it's a bigger number without knowing what it's really about. I mean, on the store shelf one says 32, the other 64. Of course a guy would buy the 64, right? It's only $50 more..
For someone that used to program in 80286 assembly language (Microsoft DOS), this stuff just whizzes over my head now. What happened..? My snowblower knows more about computers than I do today.
Oh heck - a little reading while I type this. I'm running 686-pae, apparently a 32-bit kernel. It seems all I need to do is install a different kernel (linux-image-amd64 - Linux for 64-bit PCs) to go 64-bit, but what could the reason to do that be? Even all of the software could be replaced with 64-bit stuff, but again, why?
Those are just rhetorical questions, but I would really like to know why Openoffice (aka StarOffice, LibreOffice) says it will load Access files, but won't load Tool Log... I'm guessing that Microsoft changes the format to prevent it from happening and I'm just out of luck.
Time for a bowl of Cheerios. :grin:
RE: Tool Log - Database - Sunset Machine - 11-24-2013
Egads, I do rattle on. A geek search turned this up:
In a nutshell, all modern Intel and AMD processors are 64-bit processors. 64-bit processors can run 64-bit software, which allows them to use larger amounts of RAM without any workarounds, allocate more RAM to individual programs (particularly important for games and other demanding applications), and employ more advanced low-level security features.
Another note said newer firmware requires 64-bit and that there is actually better performance with 64 over 32.
I was half-right and half-wrong. :)