March 25, 200322 yr So I have an upgrade to a runtime solution, which will include an Import script (why make customers do all the work?). The problem is, some of the files in the original solution won't let the data be imported into the new solution. In setting up the import, when I get to the setup dialog box (to match field names), all the fields in the old solution are listed as "access denied". This doesn't happen with all of the old files, just some of them. Since they all have exactly the same access privileges, I can't make head or tail of this. What could be causing the snafu?
March 25, 200322 yr Author Nope -- exactly the same. It's the first thing I checked. It's really weird.
Create an account or sign in to comment