Questions, comments and concerns about MP3-Boss: MP3 Database and Manager
You are not logged in.
I am starting to play with Access2010, 64-bit.
If I can get this to work ... it really brings the MP3-Boss engine up to date ... but maybe too up to date? How many of you are running under 64-bit Windows?
If you aren't running now, when will you be running a 64-bit computer?
How many of your are running Mp3-Boss on something earlier than WinXP (e.g., Win98)?
I'm using Vista-64.
After spending a few hours working to try to convert MP3-Boss to 64-bit Office format, I found out the following:
1) It will be a lot of work ... all API calls need to be checked to change pointers from long to the newly created datatype longptr. Doesn't sound like much ... but there are over 500 API declarations in Mp3-Boss -- lots of work! Unfortunately, it can't be automated because many longs really are just longs...
2) 64-bit Office applications can't use 32-bit Activex/COMs. This is a big one, since the developers of the Activex/COMs in MP3-Boss haven't even provided a schedule for conversion (assuming they convert)...
Microsoft is recommending Office 32-bit (even if running under 64-bit OS) because of the above -- so I've gone back to 32-bit Office. I'm happy to say that Mp3-Boss starts up under that environment (64-bit Win7) without haven't to change anything (although still some work to do!).
(52) Bad File name or number
I searched the forum and didn't see this issue. I get this error after using the duplicate search and while trying to delete a duplicate file.
I am using Windows 7 Professional, 64-bit.
I have used this feature for years and it worked great - but now...
I have Optimized the Database and Data.
I am using version 0.0683
Thanks in advance
Last edited by snordyke (2015-02-22 12:11:10)
Is there any information in the mp3boss.log file? If not, do you see any indication of the filename that is causing the problem?
Most likely there is a directory that ends up being longer than 255 characters that can't be converted to a shortfilename -- either because of an disallowed character or because short filenames are disabled.
If you can locate and rename the directory (or filename), then that should fix the problem.