+- 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 - EdK - 05-21-2012
(05-21-2012, 04:58 AM)Mayhem Wrote: I am certainly no expert Ed. In fact, I pulled this database together with a lot of help from an Access forum. I'll see if I can figure out what changes to the code need to be made. The problem is that I don't have a 64 bit system to test on.
Mayhem,
My notebook computer is running 64 bit Windows 7 so you could send me the file and I can do the testing. Although your database runs fine on that computer but I might have it running in 32 bit mode.
Ed
RE: Tool Log - Database - Mayhem - 05-21-2012
Ed, the current version is the one posted in the file section. I wonder if deleting the macro called "Autoexec" would make the difference. Open the database, press F11 and then select the macro
RE: Tool Log - Database - Sunset Machine - 05-21-2012
No go for me. It's Windows specific and apparently tied to particular (and obsolete?) versions. Wud you do that for?! :)
http://www.windows7sins.org
RE: Tool Log - Database - Mayhem - 05-24-2012
Hi sunset - what version are you using? The database should be compatible with the newer versions, with the exception being the 64 bit version. I'm trying to look to see if I can sort out the 64 bit issue.
RE: Tool Log - Database - Mayhem - 05-24-2012
Tom and Ed,
Here a copy of the front end of the database with the Autoexec macro removed. Simply replace the current Tool Log.mdb file (C:\Tool Log\Data\Tool Log.mdb) with this file.
Ed, as this is just the front end, it will not affect your data, which is stored in the back end. However, you may wish to rename the current front end, so you can retain the autoexec macro for future use.
[attachment=1706]
To open the main data input form, select "frmTool_Log" from the Form menu in the database window (see below).
[attachment=1707]
I'm not sure this is going to fix the issue you are having Tom but as this is the first thing to run, it is logical to try excluding it to see if it makes any difference.
RE: Tool Log - Database - TOM REED - 05-25-2012
GUESS I AM JUST TOO STUPID I GIVE UP. TOM
RE: Tool Log - Database - Sunset Machine - 05-25-2012
(05-24-2012, 10:41 PM)Mayhem Wrote: Hi sunset - what version are you using? The database should be compatible with the newer versions, with the exception being the 64 bit version. I'm trying to look to see if I can sort out the 64 bit issue.
Libreoffice, not having any luck importing Tool Log. Sounds like it should just open it up, but maybe I'm reading this wrong:
' Wrote:Base is the database front-end of the LibreOffice suite. With Base, you can seamlessly integrate your existing database structures into the other components of LibreOffice, or create an interface to use and administer your data as a stand-alone application. You can use imported and linked tables and queries from MySQL, PostgreSQL or Microsoft Access and many other data sources, or design your own with Base, to build powerful front-ends with sophisticated forms, reports and views. Support is built-in or easily addable for a very wide range of database products, notably the standardly-provided HSQL, MySQL, Adabas D, Microsoft Access and PostgreSQL.
Opening the zip shows several files. Pointing Base at one of the data files just put binary characters on the screen. Any ideas?
At the moment, I'm with TOM.
RE: Tool Log - Database - Mayhem - 07-01-2012
Hi Sunset - sorry, I hadn't seen your response earlier. In terms of importing the database into another program, I cannot help you. I do not know enough about Access or the program you are using to offer any help.
One thing that may be causing you issues is that the database is a split one. There is a front end, which contains the user interface and codes and a back end that contains the actual data. The reason for the split is that I can modify the front end and it will not affect the back end. Therefore, if I update a form and change some functionality, anyone using the database can update their front end and not risk losing their data.
Both the front and back end files are located in the 'Data' folder and are named "Tool Log.mdb" and "Tool Log_be.mdb" respectively. The visual basic code for the modules etc is in the front end file.
RE: Tool Log - Database - Mayhem - 11-05-2012
OK - I have posted this problem on the Access forum where I got a lot of help in building the database, so hopefully I will have a fix for Tom (and anyone else using a 64-bit system).
RE: Tool Log - Database - EdK - 01-09-2013
(11-05-2012, 06:22 AM)Mayhem Wrote: OK - I have posted this problem on the Access forum where I got a lot of help in building the database, so hopefully I will have a fix for Tom (and anyone else using a 64-bit system).
Darren,
Any update on this?
Thanks,
Ed