stiebs
Contributor
Not sure if this should go in the computers forum or the DIY
Despite all its shortcomings, I don't mind SDM too much. But my biggest gripe with it (and with all other dive log software I've tried) is rather poor printing support. So I set about seeing what I could do with SDM now that all its data is in Access.
Here's my work so far:
http://froop.net/files/scuba/d9xtras.zip
In the zip is another Access database, which contains a few queries, a code module and a couple of reports. To add it into your DB:
1. first make a backup copy of d9.mdb
2. Open d9.mdb in Access (password is "koira")
3. Open d9xtras.mdb in another instance of Access
4. Drag all the queries from d9xtras into d9
5. Drag the "ReportUser" table across
6. Drag the two reports across
7. Drag the module across
8. Go to the Queries tab on your d9.db, and you should be able to run any of the queries to give a much better view of your dive log data.
9. Hit ALT-F11 to bring up the VBA editor.
10. Go to Tools>References and find and tick Microsoft DAO 3.6 Object Library
11. Close the VBA editor
12. Double-click the "Users" query, and check what your userID is.
13. Double-click the "ReportUser" table, and update the UserID with yours.
Now you should be able to double-click the "DiveLog" report to give a nice pretty divelog. Its quite small, but that's because I print my logs in a diary-sized notebook, about 4"x7"
This is what it should look like:
http://froop.net/files/scuba/DiveLog.pdf
I'm sure there's an easier way to export/import all this.
There's still plenty of glitches and also a lot of data I haven't yet deciphered. I use metric. I have no idea what will happen if you have your data stored in imperial. Cylinder pressures are dealt with differently if you have a default cylinder instead of entering one for each dive.
The sub-report will create a second log-page showing any pictures that have been added as annotations, along with their notes. But I think that some of the object reference may be lost in the copying across.
Despite all its shortcomings, I don't mind SDM too much. But my biggest gripe with it (and with all other dive log software I've tried) is rather poor printing support. So I set about seeing what I could do with SDM now that all its data is in Access.
Here's my work so far:
http://froop.net/files/scuba/d9xtras.zip
In the zip is another Access database, which contains a few queries, a code module and a couple of reports. To add it into your DB:
1. first make a backup copy of d9.mdb
2. Open d9.mdb in Access (password is "koira")
3. Open d9xtras.mdb in another instance of Access
4. Drag all the queries from d9xtras into d9
5. Drag the "ReportUser" table across
6. Drag the two reports across
7. Drag the module across
8. Go to the Queries tab on your d9.db, and you should be able to run any of the queries to give a much better view of your dive log data.
9. Hit ALT-F11 to bring up the VBA editor.
10. Go to Tools>References and find and tick Microsoft DAO 3.6 Object Library
11. Close the VBA editor
12. Double-click the "Users" query, and check what your userID is.
13. Double-click the "ReportUser" table, and update the UserID with yours.
Now you should be able to double-click the "DiveLog" report to give a nice pretty divelog. Its quite small, but that's because I print my logs in a diary-sized notebook, about 4"x7"
This is what it should look like:
http://froop.net/files/scuba/DiveLog.pdf
I'm sure there's an easier way to export/import all this.
There's still plenty of glitches and also a lot of data I haven't yet deciphered. I use metric. I have no idea what will happen if you have your data stored in imperial. Cylinder pressures are dealt with differently if you have a default cylinder instead of entering one for each dive.
The sub-report will create a second log-page showing any pictures that have been added as annotations, along with their notes. But I think that some of the object reference may be lost in the copying across.