Re: ACCESS migration error

[s.opelt]

At first it was saved remotely with a name like foo.2005.01.15.mdb which seemed to totally confuse the tool because the schema name which i could select was just '15'.

I changed it to just foo.mdb which did not work. When I copied the file to my local disk as foo.mdb it was fine.

Its also a bit strange that the connection test seemed to pass.

For privacy reasons I cant post the full URL of the file but the only special chars contained are a space and a '$'-mark in 'userhomes$'.


Simon