Thank you for responding to my call of need
- Why are you not using QlikView server for the reload?
The report cannot reload by itself atm because the used ODBC connection cannot use UNC to allocate the access DB.
To go arround this i mapped a drive so i can use that mapped drive ( p: in this case ) in the odbc connection.
When the drive mapping is present ( when i am logged in to the QV server) i can use the server reload. But when i schedule the reload in QV i cannot make the drive mapping.
Therefor i tried using the command line interface.
- Is the drive letter also mapped for the user running the reloads?
The user running the reload is a seperate user and does not have the drive mapping i need for the odbc connection. Hence me trying to script it in the cmd file.
I hope this clears some questions.
Small update :
You can use UNC naming in the OBDC.
How? Just type it in the filename box when you create a new OBDC connection. This is a bit silly imo because the ODBC ui does not have any buttons or something to support this. This can be classified as a small "You need to know" issue.
Now that i can place UNC inside the ODBC i can reload from the QVS Schedule itself
Well, it should be possible but then i stumbled upon another part of my problem, Authorisation is also an issue.
The access on the filesystem is prohibeted because the DB contains data from the personal. Access is granted under strong supervision. I got acces so now i can "see" the DB at least.
To access the data inside the DB i need to use a different user, which has been configured inside the master DB.
Long story so far...hang on we are getting close.
What i learned so far:
1. The authorisation that is checked is from the person logged into the QVS making the ODBC connection.Regardless of the credentials that you can supply configuring the connection because those are used to access the data insde the DB, not the filesystem. So the user setting up AND Using the connection needs to be granted acces on filesystem level.
2. QVS Schedule runs as a service! This service cant use drive mappings nore create them.
3. You can use UNC inside ODBC connections, just type them inside the name field!
My problem was a mixed one. I am working now to get the authorisation correctly configured by our system admins. The UNC inside ODBC is solved so there is no need for drive mappings etc.
Eventhough it isnt solved atm i am sure it will be very soon.
Thanks for the help, it is much appreciated