|
Home > Archive > Programming with dBASE > December 2006 > Conversion Conundrum
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Conversion Conundrum
|
|
| Jan Hoelterling 2006-12-06, 7:13 pm |
| Hi folks,
I need to convert data from a legacy app where I have to USE the input table
because I need to get deleted records, as well. Unfortunately, the table has
a field named FORM, which - of course - makes everything in the form blow
up. Any idea how I can resolve this?
It's not a one time deal, I need to deliver the conversion program to a
couple hundred people, so just going into the designer and modifying the
table is not an option.
Thanks in advance for any ideas!
Regards,
Jan
| |
| Bruce Beacham 2006-12-06, 7:13 pm |
| Jan Hoelterling wrote:
Assuming this conversion is done once for each site and the users at
that site then use your new suite -
> I need to convert data from a legacy app where I have to USE the input table
> because I need to get deleted records, as well. Unfortunately, the table has
> a field named FORM, which - of course - makes everything in the form blow
> up. Any idea how I can resolve this?
To get the deleted records back:
Use <table>
RECALL ALL
USE
Then you can employ OODML.
Bruce Beacham
| |
| Jan Hoelterling 2006-12-06, 7:13 pm |
|
"Bruce Beacham" <bbeacham@beacham.no-spam.co.uk> wrote in message
news:nIeuwzTGHHA.1140@news-server...
> To get the deleted records back:
Ah yes, but then I won't know which ones WERE deleted!
Thanks for the suggestion, Bruce.
Jan
| |
| Paul Van House 2006-12-06, 7:13 pm |
| In article <1j3dXvTGHHA.1140@news-server>, jan@hoelterling.com says...
> Hi folks,
>
> I need to convert data from a legacy app where I have to USE the input table
> because I need to get deleted records, as well. Unfortunately, the table has
> a field named FORM, which - of course - makes everything in the form blow
> up. Any idea how I can resolve this?
Refer to the field as
[Alias]->Form
Assuming the table name is "stuff"
Use Stuff
?Stuff->Form
I think this will work.
Or, use Bruce's suggestion to undelete the records so you can use OODML.
--
Paul Van House
remove "_removeme" for e-mail replies
Radio/TV Software and Baseball Stat Software:
http://www.binxsoftware.com
Family Home Page: http://vanhouse.binxsoftware.com
| |
| Lysander 2006-12-06, 7:13 pm |
| Bruce Beacham schrieb:
> Use <table>
> RECALL ALL
> USE
Yep!
And if you should still need the information, which record was
marked "deleted" you could employ "set deleted off" in the
introduction, ADD another field (WASDeleted, logical), replace all
WasDeleted with deleted(), and THEN recall all, set deleted on, go
OODML..
| |
| Jan Hoelterling 2006-12-06, 7:13 pm |
|
"Paul Van House" < pvanhouse1_removeMe@
houston.rr.com> wrote in message
news:MPG. 1fe0851a4c2eef329897
0c@news.dbase.com...
> Refer to the field as
> [Alias]->Form
That seems to work, indeed!
Thanks, Paul
Jan
| |
| Jan Hoelterling 2006-12-06, 7:13 pm |
| Thanks, Andre.
I was able to solve it by using the file in a different alias so that FORM
is the Form and B->FORM is the field from the table.
Jan
| |
| Marc Hamelin 2006-12-06, 7:13 pm |
| You could create an array and store the values of the main key field for the
deleted rows, and then recall them. That way you would know which ones are
which.
DeletedRows = new array()
use "yourTable"
set deleted off
do
if deleted() == true
DeletedRows.add(yourTable->KeyField)
recall
skip 1
else
skip 1
endif
until eof() == true
set deleted on
close tables
Hope this helps.
Marc Hamelin
Jan Hoelterling wrote:
> "Bruce Beacham" <bbeacham@beacham.no-spam.co.uk> wrote in message
> news:nIeuwzTGHHA.1140@news-server...
>
> Ah yes, but then I won't know which ones WERE deleted!
>
> Thanks for the suggestion, Bruce.
>
> Jan
|
|
|
|
|