Dialog Form: Cannot Paste Data

[rtbtat]

Hi:

The president of my old computer club just advised me reference a problem he is having with an old application I wrote a couple of years ago. This is a unique little problem I never noticed before, but I'm confident someone on this board will provide a quick answer.

I created a simple form based upon a One to One set so the user can enter data into MEMO fields. If one opens the form by itself, you can either type data and/or use Ctrl-V to PASTE data into the memo field.

However, if he opens that same form via a button on the Membership form in "DIALOG" mode, the use can manually type new data into the memo field but he/she cannot PASTE data via Ctrl-V. Isn't that somewhat bizarre?

Is there something about the built in properties of a dialog form that will allow manual data entry but will NOT allow the user to PASTE data?

Thanks,
Robert

[Daniel Weiss]

RE: Dialog Form: Cannot Paste Data

Robert, you might be correct the Ctr-V doesn�t work in a dialog form but if the user would use the right click of the mouse they would be able to use the past option. It seems that using the Ctr key is one of the many limitations in a dialog form, in the other hand there are many Advantages to the dialog form

Daniel Weiss

[Tom Cone Jr]

RE: Dialog Form: Cannot Paste Data

Robert, will Ctrl-V paste the text into the memo field after the user begins an edit to the current memo? I'm wondering if the memo field has focus, and is in change mode, when the user is trying to begin the paste?

-- tom

[Edward F. Schulz]

RE: Dialog Form: Cannot Paste Data

Hi Phorum,

This question does not help Robert, but it is somewhat related. From
time to time I see a negative attitude toward using memo fields. This
is worrisome to me since I have 3 major apps that employ a memo field.
None of them have extensive text but none the less are important. Can
anyone explain the downside of a memo field to a novice such as me.
Given the fact that they might be extremely counterproductive to the
performance of the app, is there a way that I can construct an
operation that will change them to a character field?

As always .... many thanks for your time,
efs

[Daniel Weiss]

RE: Dialog Form: Cannot Paste Data

Tom, I think the Ctr-V doesn�t work in any way in a memo field if the form was opened as a dialog but it works in any other fields in a dialog form.

Daniel Weiss

[rtbtat]

RE: Dialog Form: Cannot Paste Data

Hello Tom:

You can type new data into the memo field, you can edit and/or delete current information in the memo field, but you cannot paste new data. In other words, the form works as designed with that lone exception.

Robert

[rtbtat]

RE: Dialog Form: Cannot Paste Data

Hello Edward:

I cannot speak for anyone else, but I've personally had problems wherein the memo file [FPT] grows exponentially in size. And I mean it becomes huge, far larger than one would expect in relation to the amount of data being stored.

More importantly, if you try to import an Alpha Five data file as DBASE IV into Access 2000, you cannot do such until you delete the memo field.

That's why when I decide that I need Memo fields in an application, they are not part of my main data tables any more. I instead use Memo fields as the child table in a One to One link [SET]. That's what I did in this case, when the user is on a Member's record, he/she clicks on a button that opens the memo field for that particular member, the form is linked by the Member_ID number. I've found this type of set up eliminates the two types of problems I described above.

In sum, I keep all of the member data in the main data table [dbf file] while all pertinent data that belongs in the member's memo field [fpt], is kept in a totally separate file linked by Member_ID.

[Daniel Weiss]

RE: Dialog Form: Cannot Paste Data

Try this, add a separate table that holds the memo filed and attached it in a set to the parent table, on your entry set the memo field to read only, put a button on that form that opens a form in dialog mode that contains the memo field.
Since I used this method I have no problems with memos at all
The credit for this goes to Dr Peter Wayne, I followed his guidelines

Here is an example script for the button
dim mode as c
mode = parentform.mode_get()
if mode = "ENTER" .or. mode = "CHANGE"
parentform.commit()
if parentform.mode_get()"VIEW"
ui_msg_box("Unable to save your changes","Please correct and save,
or discard your changes", UI_STOP_SYMBOL)
end if
end if

inv = inv_no.value
if inv =""
end
end if

tmemo = table.open("imemo.dbf")
idx = tmemo.index_primary_put("invno")
rec = tmemo.fetch_find(inv)
if rec > 0
goto openform
else
tmemo.enter_begin()
tmemo.inv_no = inv
tmemo.enter_end(.t.)
end if
tmemo.close()

openform:

DIM layout_ptr as P
f = :Form.load("ENTER_IMEMO","dialog")

f.index_set("invno")
f.find(inv)
f.activate()
f.show()

last_button = f.last_pressed()

if last_button = "FINISH"
f.close()
end if
inv_no.Activate()
parentform.Resynch()
end

Daniel Weiss

[rtbtat]

RE: Dialog Form: Cannot Paste Data

Hi Daniel:

I'm sorry, I inadvertently attached my reponse to your last message when it should have been attached to Edward's response. I think he was the guy who asked why some people are hesitant about using memo fields and I was merely trying to give him one person's experience plus a solution that at least works for me.

Thanks for your detailed response but I already do something very similar. As described in my previous message, I keep the member's memo field in a totally separate table that is part of a One to One set that is NOT in my current set, but is linked via the Member_ID field.

So far Daniel, I haven't found a specific need to include the aforementioned memo set as part of the same set where membership data is stored. I always prefer smaller sets to larger ones that slow down data entry.

Thanks,
Robert

[Peter.Greulich]

RE: Dialog Form: Cannot Paste Data

Ed,

There are two schools on Memos: With'em or agin'em. Some like me, have had no problems in ver4 and up. Others like Robert suggest the cautionary approach - linked "memo tables". Not a bad idea. Recently I saw a memo file flate to about a zillion GBs. But that was because I had removed the fpt file from the associated table (I was running a test). Really no problems in my humble experience - but, others have expressed some.

BUT REMEMBER! In any case, Alpha uses memo fields internally to store your reports, forms, scripts - whatever. That's what the ddm and sem files are! You really can't get away from them, even if you want to.

Peter