Using Local tables instead of entreprise server


We are using OW version XE

We want to be able to change a table already on the enterprise server (add a
few fields) but want to do it on the local workstation only without
affecting the version on the server. The program will be changed on the
workstation using the local modified table.

Later when all is tested, we want to replace the changed table on the
enterprise server and check-in the program without any additional changes to
the program

Can this be done and what is the best procedure to accomplish this ?

Lorenzo Cefaloni
EDS Canada Inc.
* 800, boul. Rene-Levesque Ouest
Montreal (Quebec) H3B 5G8
* (514) 390-2038
* (514) 866-8427
[email protected]

is this a OneWorld table or a custom (non JDE) table?

Tell me/us that this is a custom table and not a standard JDE/OneWorld table. You really, really should not change the standard JDE tables!

Also why not use DV7333 instead of the local Access database? That way your developer's and testers can share the same table.

Very briefly what you need to do (for a custom table) is:
1. Change the OCM mapping to "OneWorld Local - **7333" for the environment and developer that will be doing this work.
2. Make changes to the table specification (add fields) using OCM.
3. Generate the table in the "OneWorld Local - **7333" (JDEB7.mdb) data source
4. If you need test data come up with a way to copy data from the old table into the new one (this can be done using Access and ODBC).

when testing is done you will need to delete the OCM mapping, copy/promote the table specs to the other path codes, and determine whether you keep the data in the existing tables (in which case add the new fields outside of oneworld) or blow away the existing data (in which case just regenerate the table).

Net, net this approach is a bit messy. Maybe someone else can describe a better way?

Larry Jones
[email protected]
OneWorld B733.1, SP 11.3
HPUX 11, Oracle SE 8.1.6
SandBox: OneWorld XE SP15

Larry is right (as it is usual :)
Just an alternative:
What about to create a Custom Path Code and a Custom Environment for this types of developments. In this case you can create the table on the server, you can Check-In the object, so you can develop and test on several machine not only on single.

You can find white papers, documentations on the KG how to create Custom Path Codes. If you are on XE then you have to configure your Object Management for that path code too. There is a documentation about this issue (ott-00-0068 "Configuring Object Management Workbench with Custom or Additional Path Codes") on the Knowledge Garden.

Maybe this solution is a shooting with canon to a bird in your special situation.


B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)