Simple reply - Yes.
On the NL website for each game you can download (as CSV) the Results History for the last 180 days.
I do this then have routines to import them into Access to process them. The change of file name prevents this happening.
The perfect reason for using a decimal data type in your dbms, and one of the reasons Access needs a native decimal data type. You will always get a consistent answer (even if it isn't perfect).
This may be a thread which hasn't been edited in a while but such problems just don't go away.
My latest annoyance is the UK National Lottery once again where after a re-vamp the drawhistory download for just one of the games has changed its filename to replace 2 of the 3 hyphens to spaces...
I'm delighted that Isladogs pointed me in the direction of FormattedMsgBox and despite its marginally different behaviour am happily now using it.
I am unable to find, however, any reference to how or why it works and what exactly Eval is doing in this case. Can enyone help?
Of course we will move on: the decisions have been made. The points in your bulleted list are all laudable but don't explain a hugely intrusive title and removal of the title bar. And anyway the highlighted heading was always optional so dislike was catered for.
Can make arguments for both. Down the pub it would be great fun to argue this for hours - unfortunately no so much so here, so I won't bother to take it further. 😄
One app being ruined is enough!
I re-iterate one of my posts above - 'if it ain't broke don't fix it'. The new MsgBox is proof of this. It wasn't broke but it was 'fixed' anyway nd now doesn't work - no bolded first line.
The new style message box might be acceptable if it still allowed the bolding of the first line of the message. This not being there alters the logic of messages for people who use the split message features abeit WizHook or FormattedMsgBox.
The logic of its use is (for people who used the...
The German system is a bit of a hybrid: compulsory insurance, normally taken from your pay! You want more than the basics, you pay. It's not quite as simlpe as that in reality, of course.
As you might imagine blind panic immediately set in: I had always used the WizMsgBox as though it had the arguments in the MsgBox order and it worked.
Then I did some archaeology in my ancient documentation (2004) and found my own function I which was using - WHMBox - had them in 'proper'...
As a postscript to this thread I cannot but say Thank you once again to isladogs for making me aware of the formatted message box which still works as wizhook message box did (and, of course, the Access message box in days of yore.)
Adding the code then a simple find and replace of wizhook with...
Thanks - I have read your article which, although interesting, doesn't address the 'Problem' (mine I admit) that the logic of the revised box has changed. I still maintain that this was a change purely for the sake of change and totally unnecessary. If they wanted to change a dialog why din't...
Have just been in the position (eventually) to try formatted message box - will be adopting generally as it does what I want in a rational, logical manner,
Thank you Isladogs for pointing out its existence.
PS I hope this doesn't change too !
Two minor points - I described the bold line as a heading. Secondly, of course it doesn't go against the rules of eEnglish: I should have said it encourages users to go against them.
Back to the change of style there is one truly important fault with the new style message box. It stops the WizHook variant working properly.
I like many coders use this as it replicate(s/d) the original Access Message box where separating the text of the message with the @ sign divided it...