Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
MULTIPLE MEMO FIELDS IN ORACLE
Message
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00523180
Message ID:
00523428
Views:
21
>Step 1 : Using VFP Upsize Wizard, create tables at Oracle DB with VARCHAR default for Memo. Whatever other modification required at Oracle DB like Remote Store Procedure,views,Default & Index.

I turned away from the Upsize wizard and write my own. It's relatively simple.
Just use AFIELDS and loop through the columns to create a CREATE TABLE
COMMAND and INSERT STATEMENTS.

>Step 2 : From Oracle DB, Drop VARCHAR (MEMO ) OR Modify structure with CLOB for all MEMO.( ORACLE allow you to create multiple CLOB ( 4 GB capacity) fields in single table.
I used varchar2(4000) columns as my memo fields.
Rather than CLOB.

>Step 3 : Create Remote View using ORACLE DB connection.

I looked at doing this but found that as soon as I opened the DBC in the traditional way the app would suck back all available memory on the PC.
You might consider trying ADO or OLE Objects for Oracle or SQL passthrough.
(I use ADO) Of course this requires much more recoding. But the way that foxpro deals with data is just not compatible with oracle so I imagine you will require
some recoding anyways. (I suppose my main problem wa sthat previous developers just opened all the tables at the start of the application and then proceeded to write code which would loop through the entire table.


>Step 4 : Convert all SQL STP or Pure SQL for remote data compatible with ORACLE.( Here someone help us with detail about difference between ORACLE SQL / SQL Server SQL & VFP Native.

I try to rely on the ANSI based SQL alternatives on SQL server. When you do this and do not try to use any special T-SQL or PL\SQL the SQL is basically identical. VFP native is also similar...

You should perhaps rely on stored procedures as much as possible, In my opinion just use them everywhere. Stored procedure code is dramitically different. If you use cursors (should be avoided where possible.) The syntax on SQL Server has two forms. If you use the ANSI complient for the Oracle migration wizard can convert all SP's to Oracle. (it's actually very cool..) There is also one for VFP 3.0 but I didn't try it yet.

HTH
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform