Import from Development to Production Woes

[sjpistolesi]

[newly upgraded to ACC2000; Windows2000]

I am having serious problems importing into [existing] production version of an application, new/revised forms and their modules from the [different network location] development area. Why???

Symptoms I've observed:

[1] When using import from the production version of the application, the forms are not coming into the database from the other location.
[2] Created fresh [empty] database in the production network location and imported from the development location the forms and modules. But, then the imported forms could not "see" their event modules, even though they were in the same database.

What is going on here???? What embedded features of the Windows2000 core are impeding such normal development and production functions? This never happened when our network was NT4!!!!


The only way I could get the developed forms to production was to copy the development version then paste it into the production location and rename it, then open it.

Sandy

 

[grnzbra]

Is the code written in ADO? I seem to remember that unlike opening a recordset with

set db = currentdb
set rs = db.openrecoreset etc etc

ado uses the statement of a connection to the data source. If you've got something like this, when you copy the form, it may still be looking for the other database.

I'm not at my Access2000 system at the moment, so I can't check; just a swag from a distant memory of programming this way only once (a long time ago in a galexie far away)

 

[sjpistolesi]

Yes, there are some ADO connections, but only to "current project.connection" ... nothing outside the current project to another project or xBase.

Sandy