Restructure table, language driver

[VAS]

I need to set the language driver to Paradox 'ascii' on a Pdx 4 table created from a
Pdx 5 table (using transferData). The Pdx 5 table has language driver 'ascii' ANSI

I can manually Restructure->Language Driver->Paradox 'ascii' and save the table.
However, using this code the language driver is not set:

tbl.attach ("NMaster4.db&quot
dynNewLD["LANGDRIVER"] = "ASCII"
tbl.restructure(dynNewLD)

No errors are reported and if I add

dynNewLD["saveas"] = "testing"

I do get a table named testing, so I am assuming my restructure command is okay.

My BDE shows that Paradox 'ascii' is the langdriver for Paradox. Any new table I create defaults to Paradox 'ascii' for the language driver. Running sysInfo
shows LanguageDriver ascii.

Any ideas?

Victoria

 

[footpad]

Victoria,

Which version of Paradox are you using. Also, what's your BDE version. That'll help shed some light.

-- Lance

 

[VAS]

It's Paradox V9.00.368 and BDE Adminitrator V5.01.

The annoying thing is, this is all part of a MS Access program I wrote in April. It
worked beautifully then and in June. Since then I have (1) rebuilt my PC and
(2) installed Office 2K -- but remained with Access 97.

The source table (in Pdx 5) has had no changes to it, and the reason I convert it
to Pdx 4 for the Access is that (at the time) it worked that way.

Thanks,

Victoria

 

[VAS]

I need to amend what I just said. Previously, I only had to do the data transfer; the table restructure was added after the link table (in Access) failed due to the language driver.

V

 

[footpad]

Victoria,

Off the cuff, it sounds like you might need a service pack update for Paradox 9. You can obtain the latest from Corel. Unfortunately, it's only available by calling their customer service number and requesting WPO2K/Pro SP4, which does work for Paradox 9 Dev. Ed. There's a nominal charge for S&H. The phone number is on their web site.

I presume you're using OLE automation from Access to control Paradox?

Make sure you've got MDAC 2.6 installed; it's available from MS's download pages. I beliee it's in the Data section.

Also, you may need to recheck your BDE version; v5.01 sounds like the version of the BDE Administrator applet in Control Panel. For more details, please see

http://www.techtricks.com/paradox/bdeversion.php3.

Hope this helps...

-- Lance

 

[VAS]

Thanks, Lance. I ordered the SP from Corel; we'll see if that helps.

I went ahead and installed MDAC 2.6 as well as upgrading my BDE. I was looking in the wrong place for BDE version -- thanks for the tip.

It seems it has to be a Pdx problem, since I can't programmatically restructure a table to a new language driver, while I can do it manually.

Thanks for all your help. Any other ideas are welcomed!

Victoria

 

[footpad]

Victoria,

I'll confess that Paradox's restructure method has been problematic from day one.

You may have better luck maintaining several copies of the empty target table, each using a relevant language driver. Copy seems to work far more effectively than restructure. Why? I don't know. (Well, I do know, but that's old history.) AAR, the point is, it's better to keep a library of acceptable structures and then use copy() to overwrite the target structure.

If you can restrict the language driver to a set of known values, you _can_ ship several temporary tables, each using the desired language driver. At runtime, determine the appropriate one and then copy it from your library of temporary tables, each of which uses a separate language driver.

I know it's a lot of work and extremely counter to the eay we're used to thinking, but it does work...in the end, that's what we're after, right?

-- Lance