Copy() method of UpdateSet() does not create complete table

Article View: borland.public.vdbase.data.sql

Article #1159

Back to borland.public.vdbase.data.sql Previous Next

#1159

From: Nedim Buyukmihci
Date: Wed, 22 Apr 1998 00:00

15 lines
1068 bytes

VdB 7.01 (b1419)

This may be 'working as designed' but it is frustrating. Online Help
states that the copy() method of UpdateSet() will "When using a table
name as a destination, that table is created, or overwritten if it
already exists."

A problem is that it only creates the .dbf and, if exists, the .dbt.
The production index (.mdx) file is not created. The online Help
statement implies that the table, not select components, is created.

Is this 'working as designed' or a flaw in the method?

Ned

Technical Details

Message-ID: <353e0cea.3458978@forums.borland.com>

Path: arc1-ca.pugleaf.net!unknown!not-for-mail

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: ff5a1,ce0696366d9b4317,start
X-Google-Attributes: gidff5a1,public
From: ncbuyukmihci@ucdavis.edu (Nedim Buyukmihci)
Subject: Copy() method of UpdateSet() does not create complete table
Date: 1998/04/22
Message-ID: <353e0cea.3458978@forums.borland.com>
X-Deja-AN: 346669466
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Organization: PigByte Data�
Mime-Version: 1.0
Reply-To: ncbuyukmihci@ucdavis.edu
Newsgroups: borland.public.vdbase.data.sql