Array?

[Springfield]

I need to store a record from a table temporarily and had the idea that an array would do it, A table is no good as it will be a multi user system.

I have tried initialize_from_table to populate the array but it appears to be empty ?

If I did get the data in the array how would I write it back to a different table ?

Thanks

[G Gabriel]

Re: Array?

Gary:
Welcome to the board.
An array is more suitable for an "array" of values.
With one record, an array seems an overkill, not that there is anything wrong with that.

A table is no good as it will be a multi user system

Actually, it's the other way around. An array is a variable, and as of today's primitive technology, a variable cannot be shared over a network, while values from a table can be.

If I did get the data in the array how would I write it back to a different table ?

Sounds like your whole objective is to copy a record from one table to another. There has been as many questions related to this subject as there is selicon in Pamela Anderson and just as many ways to do it. My all time preference is using xbasic to take the values directly from the source table to the target table. How do you do that depends on where you do it from, so if you offer a little more details, the answer could be more specific.

[Tom Cone Jr]

Re: Array?

Gary, let us know if an example would help you? Even better, consider posting a zipped copy of your database here so we can work on it with you. You can attach zip files using the Go Advanced button in the message editor, followed by the Manage Attachments button.

It's not necessary to store field values in an array or even in a variable in order to write them from one table to another so let us know if that why you're trying to store them temporarily before writing them again.

-- tom

ps. Welcome to the message board.

[Springfield]

Re: Array?

Thank you for your replies

I am happy copying record from one table to another but I need to keep a copy of a record in case it is changed If it is changed then write the original to another table, if not then discard

If I do this via a table then if two users happen to do the update at the same time which record is which.

I thought an array would do as it would store the data local to each user?

[G Gabriel]

Re: Array?

Now that more peices of the puzzle are forth coming, it starts to make more sense.

You can store the record values in an array, in a variable as a string, in a number of variables, in a temp table or by some other means. Or you could also take advantage of alpha's built in function:
ALLTEXT_INITIAL()

[Springfield]

Re: Array?

Now that more peices of the puzzle are forth coming, it starts to make more sense.

You can store the record values in an array, in a variable as a string, in a number of variables, in a temp table or by some other means. Or you could also take advantage of alpha's built in function:
ALLTEXT_INITIAL()

I get ALLTEXT_INITIAL() but how do I then write that back to a table when required

[G Gabriel]

Re: Array?

I get ALLTEXT_INITIAL() but how do I then write that back to a table when required

Hmmm..
Foreget about all of the above.

1-Before you make changes to the current record, duplicate it
2-Make your changes
3-If not happy with the changes, delete them, you still have your original duplicate
4-If you are happy with the changes, delete the old record.

[MikeC]

Re: Array?

If something that is to be done before someone is to leave the form in question I would think that table.record_data_get() and table.record_data_set() would work very easily...and don't think it would be affected with multi-users as it is a variable.

[Springfield]

Re: Array?

Thanks chaps

table.record_data_get() and table.record_data_set() should do it.

[Tom Cone Jr]

Re: Array?

Gary, in Ch 42 of Dr. Wayne's book "Xbasic for Everyone - Vers 8" he furnishes the code to create an audit trail for changes, deletions, and new records in a checkbook application. He uses a separate variable for each field in the record and does not use an array. His approach could be adapted easily to use a pointer variable, with each table field value occupying a separate property, but I see little to be gained by doing so. -- tom

[MikeC]

Re: Array?

Gary,

I should add that it seems that table.record_data_get() and ..._set() cannot be used on the OnInit of a form. If your form is modal then simply get it with the OnActivate and set whenever....when exiting, using a "Cancel" button, etc.... . If a user can go to a different form or anywhere that will cause the OnActivate to fire again then make the OnActivate a one-time event with a logical variable. So could have the default set to be .T. . When the form is first opened, use table.record_data_get() and set the variable to .F. . Wherever you would use table.record_data_set() or when closing the form, change the variable back to .T. .

Just thought I should add to avoid any pitfalls.

[G Gabriel]

Re: Array?

You could do something like this:
In a button (call it "Edit Record") on the form of the original table, put this script:

t=table.current()
x = tbl.record_data_get()
if alltext_initial<>alltext
t1=table.open("..target_table..")
t1.enter_begin()
t1.record_data_set(x)
t1.enter_end(.T.)
t1.close()
end if