D
dave
I've setup a macro that populates a project file with data from Access
tables. The macro uses the built 'map' method in project and worked fine in
testing. It wasn't until the project file was published as an enterprise
file that we noticed something strange. The 'map' within the macro was
setup to merge data from the Access table. The problem with the macro is it
fails to merge with the subject enterprise project file and creates a new
non-enterprise file. Is this normal behavior? If not, what would solve
this sitution?
Dave
tables. The macro uses the built 'map' method in project and worked fine in
testing. It wasn't until the project file was published as an enterprise
file that we noticed something strange. The 'map' within the macro was
setup to merge data from the Access table. The problem with the macro is it
fails to merge with the subject enterprise project file and creates a new
non-enterprise file. Is this normal behavior? If not, what would solve
this sitution?
Dave