September 2, at am No on both accounts I don't know if maybe SSIS can't load the workgroup security. Not a clue October 14, at am I received an email about this post by someone asking how it was resolved. Anyway here is what I did: I gave up Then I setup some simple cleanup queries and a Macro to kick them all off in a row. November 10, at am November 12, at am Could you show us an example, or perhaps a properties window?
So not to interfere with other users of the network database. Basically I copied it to my desktop along with the Access database, made the adjustments, exported the table to a new Access database I had setup.
So when it came time for the migration I copied the Access database to my machine, exported the table, kicked off the Macro and then a minute or two later once all my cleanup queries ran that I wanted to run in Access deleting bogus rows, rows with no actual content, etc Start your application. The workgroup information file is missing, or opened exclusively by another user. But sometimes not always, it gives me error like: Could not find a part of the path.
Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Try False first. Apparently the last item in that string is for the case where there's both a database password and a user password. If there's no database password you don't need the last item or the semicolon just before it.
You might try setting up a connection entering nothing in that window and then see what's missing in the UDL file. Message 3 of 5. Message 4 of 5. Glad it's working! But I guess you have to know exactly what to add! Message 5 of 5. I personally think it's easier to edit the udl file, but if you happen to know that the value for "Jet OLDBE:System Database" needs to be the path of your MDW permissions file you could enter it in there. It seems like they could have created some more intuitive method of picking your settings rather than the cryptic way it is done.
At any rate, thanks again.
0コメント