>Evan and others,
>
>>I will be participating in a client/server project this fall using Oracle (my first) and have a few tricks up my sleeve when I run into the inevitable gotchas.>
>
>We are just finishing up a VFP/Oracle project for the U.S. Pentagon. There are a number of gotchas you need to consider when creating a VFP application that accesses an Oracle back end.
>
>For example...
>Although VFP allows multiple memo and general fields in a single table, Oracle *does not*. The equivalent Oracle data type is "Long Raw", and you can only have one of these fields per table. To get around this Oracle limitation, you must create a separate child table for each additional memo or general field that you need.
>
>We will be publishing information regarding VFP/Oracle in our "Codebook for Mere Mortals Guide" as a service to other VFP developers. The majority of the Oracle information we will publish is not Codebook-specific, so I'm sure you would benefit from taking a look at it.
>
>If you'd like, I can let you know when the new version of the guide is complete.
>
>Regards,
>Kevin McNeish
>Oak Leaf Enterprises Solution Design, Inc.

Kevin,

Let me know when it is complete. Thanks.

The "gotchas" are the important parts as far as I'm concerned. FYI. Our project will most likely use Developer 2000 (the Oracle front end), but I will be looking really hard for any opportunity use VFP as a front end also.