Page 3 of 11
Posted: Thu Jun 12, 2008 7:51 am
by MoDementia
Why I wrote 1181 but was looking at 1081 I don't know
Anyway without the extra info I would be at a loss, Thanks
The norm is -1 not 0 for empty dates
I have re-released 1.8 with a fix to cover both -1 and 0
Download and install over the top.
Posted: Thu Jun 12, 2008 9:01 am
by nynaevelan
Ok, I'm back in business. Thanks again.
Nyn
Posted: Sun Jun 15, 2008 3:16 am
by MoDementia
New Version
' 15-06-08 Version 1.9
' Localise CDbl (Thanks ZvezdanD)
Posted: Sun Jun 15, 2008 7:07 am
by nynaevelan
MoDementia wrote:
' Localise CDbl
What does this mean exactly??
Nyn
Posted: Sun Jun 15, 2008 9:05 am
by MoDementia
In some languages full stops become commas
so the dates don't work in select statements.
Alas I'm not sure the fix worked
[EDIT] If someone that has solved this problem before could look at my code I would appreciate it muchly.
Basically I replaced all my CDbl with the following function.
It looks logical, but I'm not sure I understand it 100%
Code: Select all
LastExportDate = CDblLocale(Now)
Function CDblLocale(sExpr)
Dim lLocale
lLocale = GetLocale
SetLocale "en-us"
CDblLocale = CDbl(sExpr)
SetLocale lLocale
End Function
Posted: Sun Jun 15, 2008 6:51 pm
by MoDementia
Reverted back to version 1.8
I don't know how to fix the language problem with commas instead of full stops in internal date format.
Without having a PC with the same language settings I am just guessing if any fix will work or not
2 Issues.
1. SQL statements using 39615
,3904050926
2. Cdate function using 39615
.3904050926
If I fix one the other one is broken.
I don't know what MM might be doing on another PC so it may work for me but fail on the other PC.
e.g. are the dates stored in the DB with commas?
Is there a scripter that uses german (or some other similar language (uses commas)) that can help me fix the isssue?
[EDIT] Is it just a case of single quoting the 39615
,3904050926 in select statements and letting MM do all the other conversion?
Posted: Sun Jun 15, 2008 7:30 pm
by Bex
I might be wrong but my impression is that you only need to cater for comma vs dot problem when creating SQL queries. Meaning that whatever the locale is using isn't important as far as the VBScript code is concerned.
I just add this when I use vbs-code to write an SQL:
Code: Select all
Replace(ValueThatCouldContainComma,",",".")
Posted: Mon Jun 16, 2008 6:33 am
by MoDementia
Yeah thanks Bex I sort of came to that conclusion too.
I have had one user test it and say it is now working but I'm not 100% convinced it does/did as the communication might have been a little sketchy given the language difference.
I'm not going to release it until I get at least 1 more confirmation that it works.
Here is the 1.9 link if someone else wants to try it.
Re: Database Export\Import\Sync (DEISync) v1.8 (12-06-08) [MM3]
Posted: Sun Jun 22, 2008 3:52 pm
by nynaevelan
I have to tell you I am LOVING this script.
I just completed my first database export to a network drive in order to setup my laptop and of course it went very smoothly. It would have normally taken me hours to rescan the files via the network. Prior to using this script I was willing to sacrifice the playcounts from my work computer because I did not want to overwrite my home computer in order to keep them. But with the Import/Export sync options, I am able to save any playcounts or playlist changes which I do on my work computer. And of course let's not forget the importance of all the track editing which I complete on my home computer. Thank you again for this one, this is definately on my list of
Top 10 scripts.
Nyn
Re: Database Export\Import\Sync (DEISync) v1.8 (12-06-08) [MM3]
Posted: Sun Jun 22, 2008 7:01 pm
by MoDementia
Thanks for the praise Nyn,
It sounds like you are making full use of its functionality.
I'm actually a little jealous that I'm not in a situation to use it atm
But given that you're the only one to post in the thread, if and when I get to use it, that will make at least 2 happy campers
Actually any feedback (good or bad) is welcome by scripters, it's the only way to get a feel for whether a script is helpful to the community or not.
Not to mention that a little ego stroking goes a long way towards motivating us to write/improve some more scripts
Re: Database Export\Import\Sync (DEISync) v1.8 (12-06-08) [MM3]
Posted: Wed Jun 25, 2008 5:36 am
by nynaevelan
Hey:
I know this is probably impossible since the Now Playing list is not saved until MM is closed, but would it be possible to export the Now Playing List as well??
Nyn
Re: Database Export\Import\Sync (DEISync) v1.8 (12-06-08) [MM3]
Posted: Wed Jun 25, 2008 9:34 am
by MoDementia
Actually it is possible as long as you don't mind it clearing and rebuilding the Now Playing list when you import.
i.e. optional export but not optional import (well it could also be optional on import
)
Re: Database Export\Import\Sync (DEISync) v1.8 (12-06-08) [MM3]
Posted: Wed Jun 25, 2008 10:32 am
by nynaevelan
The optional import would be great for those situations when I want the import to overwrite the NPL, otherwise I could always create a playlist of the current NPL before running the import. I've just found there are times when I want to continue listening to the current NPL, but I lose that when I go back to listening from the other computer. As far as the export although it can be setup to optionally export the NPL, I would most likely always have it selected. Thanks for your time AGAIN.
Nyn
Re: Database Export\Import\Sync (DEISync) v1.8 (12-06-08) [MM3]
Posted: Fri Jun 27, 2008 7:41 pm
by martialartsguy
Just double-checking before I attempt to use this script:
If I have ALL my tracks on an external HD, I'm still going to have to drag it back and forth between home and work, correct?
My work doesn't like it too much when I clog their database with mp3s.
Re: Database Export\Import\Sync (DEISync) v1.8 (12-06-08) [MM3]
Posted: Fri Jun 27, 2008 7:52 pm
by MoDementia
If all your tracks are also on you home PC then you can leave your external HD at work and just put the export database on a usb stick (or email it) from home to work or vice versa
If you add a sigificant amount of new tracks at home or work its probably worth bringing the external HD home to copy those across and do a complete export.
I'm pretty sure this is exatly what nynaevelan is doing, I'm sure she would help with any specific questions via private messages.