dealio

Windows 10 Pro, 64-bit 64GB RAM 400GB free SSD disk space HomeManage 2022 (22.0.0.8) The notebook feature that is available on the properties dialog for an asset allows me to track events that happen with a particular asset. For example I track each time that I get the car serviced for maintenance, the mileage on the car and the cost of maintenance. It works well for record keeping. Recently I noticed that for one particular asset (a camera lens), I have made 9 short notes in the notebook, but only the most recent 5 entries show up in the Item Notebook section of the main window pane that displays asset summary information. Is there some way to get all the notes to show up in the list? When only some of the notes show up, it leaves the impression that the list is complete when it actually is not complete. thanks, David

Apparently not yet. I have the 22.0.0.8 (2022) version and there is no option to save an attachments folder that I can see.

There are two fields in the Asset Tracking section on the Additional tab of the Item Properties dialog box that I don't recall seeing in earlier versions of HomeManage (currently using v2022) -- did I just overlook them? Anyway, my question is how to use them. The fields are both checkboxes and their names are: Record Changes in Location Record Changes in Status & Assignment If I check these boxes, where would I find the log of changes that they record? Or is that not how they work? If not, how do they work? Thanks, David

Just recently I was updating an item and noticed that the Asset#, which I sometimes refer to when pulling up an item, can be different from the HomeManage ID. For most of my records, these two are the same, which is what I like. I'm not certain how the 2 items I've noticed today have mismatched Asset#--HomeManage ID combinations. So I have some observations/questions for clarification to help me manage items without creating a mess. What's the relationship between Asset# and HomeManage ID fields? I know from looking at the input form that I can change the Asset#, but I don't usually do that as there is no need to. The only exception I can recall is long ago I found that for several items the Asset# field contained a space preceding the number and that was causing problems for me--in that situation, for each asset I edited the Asset# field to remove the space before the number. The Barcode field matches the HomeManage ID field. Is this always true? I don't think the Barcode field is editable by me. Just an observation, not a request to be able to edit it. The asset picture files appear to use the HomeManage ID number in the filename. Can/should I edit the Asset# fields so that the Asset# matches the HomeManage ID number? Reason: I'd rather that they match to keep things simple for me, but I don't want to cause a problem in the app either. Three different examples from my database: Asset# HomeManage ID Barcode 125 122 122 <<< not sure how many items are mismatched like this 122 192 122 (note: there is no Asset# 192; how does this happen?) 190 190 190 <<< this is what I expect to find Thanks for any explanations! David PS: Forgot to mention that some time ago I did some experimenting in the database with duplicates, clones and copies of items to learn what the differences/advantages of each type of copy is. How do duplicates, clones and copies handle these 3 fields?

I believe an item can be either a parent or a child, but not both, if memory serves me. It seems like I tried this long ago, but not certain of the result. If true, that would mean there's only 1 layer of parent-child relationships that the app can track (no grandparents or grandchildren, etc.). Correct me if I've got that wrong.

This has happened to me as well in the past. It's not just you 🙂

That has been my experience as well. I think something is wrong in the application because the system date format M/D/YYYY doesn't break 2-digit months and days in any other application I use. I have a couple user-defined date fields which will not accept a second digit for either the month or the day. I don't think the developers understand the problem as I got the same response. But even if the app is using the system date format as he states, and that format is set to M/D/YYYY, date fields should still accept 2-digit months and 2-digit days. Microsoft's formatting string 'M/D/YYYY'--which is used in Windows and many MS apps, like MS Access--means display 2 digits only when the month/day is 2 digits--otherwise use 1 digit. In other words, don't pad the day and month with zeros. HomeManage uses Microsoft Access as its database. So the underlying database understands how to interpret the M/D/YYYY formatting string and will use it properly without the need to change the system date format.

I figured this out. The installer fails with the message "The setup cannot continue because the above drive does not exist." The message confused me because the drive actually does exist. The issue is that the installer is not running from the user account on my machine, but from another account (administrator). And the administrator doesn't have access to the drive. So the error message was correct if cryptic. I managed to get the install to work after learning that. It's odd though, because, though I've run into the problem before, it hasn't happened on every install of HM -- only some.

In version 2022 of HomeManage my toolbar is giant-sized and I can see no way to change it back to the normal smaller size. While this doesn't prevent me from working with the application, I would prefer to put the toolbar back to its normal size so that it doesn't unduly eat up so much screen real-estate. Please note that: the Large Icons setting in the Customize menu is NOT checked The Reset All option in the Toolbars tab of the Customize dialog box does nothing apparent, even after an application restart. the Reset Toolbar in the Standard menu of the toolbar dropdown does nothing also. How can I accomplish this? David

In version 2020 of HomeManage, I had an item in the assets database (a computer) where I put the vendor description and specifications into the comments fields as I usually do for all items. The app accepted the comments and saved the asset to the database with no issues. I've upgraded to version 2022 without any errors. But today I went to add something to the item I mentioned above and got an ugly dialog box with no title and only the words TOO LARGE! in the center. Also, the data for the item did not show up in the comments field. I double-clicked the item and the properties box showed up with all the information--even for the Comments field--correct just as I entered it in 2020. Clearly the database can hold the field's text since it appears in the property dialog box. So why do I get an error when I navigate to this item? Is this a bug?

This problem isn't a new problem. It's happened on previous versions of HomeManage as well. I run the check for updates process off the help menu and the popup show up and I click Next. The next box says "there is a new version of HomeManage 2022 available" so I click Next. It downloads a file called HM2020Up.exe (strange name -- looks like an update that is made for the previous version of HM), which runs immediately and I'm greeted by the Welcome screen. I click Next, then choose to agree with the license terms and click Next again to come to a summary screen that tells me where it will install the update. I click Next again and immediately get an error message saying "S: The setup cannot continue because the above drive does not exist." But the drive DOES exist. To verify that the HM2020Up.exe process ran in a context where the S: drive exists, I ran it from a command prompt where I had verified that the S: drive was accessible. The update process failed in exactly the same fashion. I hope we can get this issue fixed permanently, meanwhile, how can I update from 22.0.0.1 to the most recent version? David

Did your images get deleted or just not showing up in the application? I've found that if you upgrade to a new version of HM and change the default directory for the application, the install program will delete your assets.mdb file and all images as well. I had to recover from this twice with both previous new versions. I used Windows recover to recover the whole directory of images that got deleted.

MS Access is the database used for HomeManage. As someone who use to write code in MS Access, I'm aware that the single quote can cause issues when the app tries to save it to the database if it is not treated properly. There is nothing you can do, It's a bug. The same is true for the & -- it is a special character that has meaning on MS Access forms and it cause the exact results you found -- to put an underscore under the character following it. These characters have to be treated specially within the program in order to get saved properly in the database. They are bugs.

@ComputerGeek thanks for the warning!

By the way, I tried to view your video and got an error message that said the video is no longer available.