Re: Accessing foreign table thru Table conversion.
--------------9F52852E10D13BD9A2C76B71
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Minor addition. You can test your ODBC, OCM, and Environment setup by using the UTB
to query your foreign table. This saves the hassle of creating the TC program and
finding it doesn't work. TC acts odd sometimes when you change the ODBC or OCM after
creating the program. It needs to reinitialize the environment if anything has
changed.
Zoltan_Gyimesi wrote:
> Hi Balla,
>
> 1.) You have to create OneWorld data source pointing to the ODBC data
> source, similar like OneWorld Local pointing to Jdeb7.mdb.
> 2.) You have to create a OneWorld environtment too with your working path
> code and with an OCM entry, where *TBLE entry points to your new OW data
> source.
> 3.) Restart your client.
> 4.) Open the TC designer and choose your new environment as Input or Output.
> 5.) You will see your Access data source in the list.
>
> Please, let me know if it works or if you have further questions.
>
> Good Luck,
> Zoltán
>
> >
>
> --------------------------
> To view this thread, visit the JDEList forum at:
>
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OWDEV&Number=821
> *************************************************************
> This is the JDEList One World / XE Developers Mailing List.
> Archives and information on how to SUBSCRIBE, and
> UNSUBSCRIBE can be found at
http://www.JDELIST.com
> *************************************************************
--------------9F52852E10D13BD9A2C76B71
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Minor addition. You can test your ODBC, OCM, and Environment setup
by using the UTB to query your foreign table. This saves the hassle
of creating the TC program and finding it doesn't work. TC acts odd
sometimes when you change the ODBC or OCM after creating the program.
It needs to reinitialize the environment if anything has changed.
Zoltan_Gyimesi wrote:
<blockquote TYPE=CITE>Hi Balla,
1.) You have to create OneWorld data source pointing to the ODBC data
source, similar like OneWorld Local pointing to Jdeb7.mdb.
2.) You have to create a OneWorld environtment too with your working
path
code and with an OCM entry, where *TBLE entry points to your new OW
data
source.
3.) Restart your client.
4.) Open the TC designer and choose your new environment as Input or
Output.
5.) You will see your Access data source in the list.
Please, let me know if it works or if you have further questions.
Good Luck,
Zoltán
>
--------------------------
To view this thread, visit the JDEList forum at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OWDEV&Number=821
*************************************************************
This is the JDEList One World / XE Developers Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at
http://www.JDELIST.com
*************************************************************</blockquote>
</html>
--------------9F52852E10D13BD9A2C76B71--