NewsArchive
08-29-2011, 03:03 AM
Friedrich - as per a post in the C8 NG I have an issue.
For some unknown reason, every so often my CSIDL folder path changes.
Nothing goes wrong on my machine but the hardcoded paths in SB change.
For example, until a couple of days ago my SB paths used to collect my data
into the script were hardcoded into SB as C:\Users\Public\Public
Documents\....... This is direct from choosing the files from the
Visualizer.
Yesterday my scripts failed because the path had changed and dropped the
PUBLIC from Documents, so this now became C:\Users\Public\Documents \.....
I have no idea why this happens although I suspect it might be a Windows
update that does it. My Clarion apps are fine as I use Winevent to get the
CSIDL folder but it seems that SB is getting broken from time to time.
I know it is not the fault of SB but is there any way this can be avoided.
After all when using the Visualizer I am using the CSIDL folders.
If you check out the attched screenshots sb1 shows the CSIDL folder usage
and how this translates to the file properties. Now check out sb2 - this
shows the CSIDL path being hard coded into the script. That is fine until
something changes the path. When I recompile the script of course it all
fails as the path does not exist. Somehow there needs to be a mechanism that
refreshes the CSIDL path?????
Many thanks
John Fligg
For some unknown reason, every so often my CSIDL folder path changes.
Nothing goes wrong on my machine but the hardcoded paths in SB change.
For example, until a couple of days ago my SB paths used to collect my data
into the script were hardcoded into SB as C:\Users\Public\Public
Documents\....... This is direct from choosing the files from the
Visualizer.
Yesterday my scripts failed because the path had changed and dropped the
PUBLIC from Documents, so this now became C:\Users\Public\Documents \.....
I have no idea why this happens although I suspect it might be a Windows
update that does it. My Clarion apps are fine as I use Winevent to get the
CSIDL folder but it seems that SB is getting broken from time to time.
I know it is not the fault of SB but is there any way this can be avoided.
After all when using the Visualizer I am using the CSIDL folders.
If you check out the attched screenshots sb1 shows the CSIDL folder usage
and how this translates to the file properties. Now check out sb2 - this
shows the CSIDL path being hard coded into the script. That is fine until
something changes the path. When I recompile the script of course it all
fails as the path does not exist. Somehow there needs to be a mechanism that
refreshes the CSIDL path?????
Many thanks
John Fligg