FPT issue

[Mark Williams]

Re: FPT issue

This has been an on going problem with our application as well.

Would someone be willing to post a sample that has a separate table for memo fields so we could learn how to properly link the memo field table to the records?

Thanks

[Mark Williams]

Re: FPT issue

Larry,

The memo format uses binary pointers to mark the beginning and ending of each separate block of memo text. I've seen instances of corruption when users "paste" text into the memo field from word processors without first stripping out the binary print format control codes that text may contain. If your users are cutting and pasting text from other applications this may explain what happened.

is

Is it possible to disable ctrl-v in an application?

Thanks

[Tom Cone Jr]

Re: FPT issue

Mark, I think you can disable ctrl-v in a form using the onkey event to prevent the keystroke from being passed on to Windows. Don't know of a way to do it in one step across the entire application.

Would someone be willing to post a sample that has a separate table for memo fields so we could learn how to properly link the memo field table to the records?

Assuming the primary table has a single memo field you could "move" the link field value and the memo field to another table like this:
a) freeze data entry in the database. You don't want folks on the network entering or changing data while you do this.
b) duplicate the table, giving the new table a different name of course. Duplicate is an option on the utilities menu of the right click menu for your table.
c) modify the structure of the new table to delete all fields except the link field and the memo field
d) link the new table to the primary table in a new set using a one to one linkage
e) browse the set to verify that the memo field data is present twice. Once in the primary table and again in the linked child table
f) modify the structure of the primary table to delete the memo field
g) modify the forms, browses and reports that are based on the primary table. Base them on the new set, instead.

It would be prudent to make a couple of good backups of the primary table before beginning the sequence.

Before doing this let us know if you have further questions.

-- tom

[Larry Gordon]

Re: FPT issue

Having analysed all of my memo fields I have decided to take the simple, though somewhat laborious route, of replacing my memo fields with ch250 fields. I have also now established that the very large memo fields in one part of my application are running perfectly, with the damaged FPT being in another area where one specific user does most of the updating. He is particularly computer literate and always finds shortcuts. He always works with at least two instances of Alpha running, and cuts and pastes all over the place. Problem solved and many thanks for all of the input

[MoGrace]

Re: FPT issue

Hi Larry,
I wish you hadn't said that. My users are coming from a DOS program and that is exactly what they do - open multiple copies to keep from having to back out of the menu system in the DOS program. Sigh, hopefully I can convince them this ought not to be necessary in my A5 app. It never occurred to me that with an unlimited runtime license, they might be able to do this.

[MoGrace]

Re: FPT issue

N/t dupe post

[Ted Giles]

Re: FPT issue

Robin, couple of suggestions.
1. Use Throttle User Count. Won't stop everyone if you don't have them all running though but it's a threat.
2. Create a Logged in table which can be cleared nightly or on demand.
3. There should be a check somewhere to see What's Running either in Windows or AS. I'll have a look when I land later.

[DaveM]

Re: FPT issue

I have customers using the "multiple copy open" system with great success. I do have all memo fields in separate tables with maybe 3-5 fields connector, date and/or time, user name, memo. Memo fields are ONLY used where absolutely necessary and never as a crutch or catch all. This has pretty much eliminated the corruption for me. Generally, my clients are not trying to add records to both, but can use the second opening for a quick look up of name or phone or other. Explained: most dealers have the callers number show up on their phone, so they can do a number find and know who they are talking to.

2 things we need to figure out is how to keep opens to a minimum like 2 for me and the other is to stop copy-paste out of their ability

Many apps will not allow but one copy open in windows. I never worried about how they do that, but know there must be.

some kind of keyboard trap for copy and paste? does not seem enough since it can be done with mostly mouse.

[Ted Giles]

Re: FPT issue

Why multi copy open requirement Dave?
Sorry, reread the explanation.
So why not display all contacts for that site?

[DaveM]

Re: FPT issue

Ted, if they are inputting data in a form and a call comes in, they can go to the second instance with one click where the app is open in a search already rather than saving and then going to a search. That would be a minimum of 2 clicks depending where they are in the input or printing delivery reports(forms to sign) where it could be several clicks at best.

[Ted Giles]

Re: FPT issue

Understand. I had that situation a few years back with a recruitment and staff agency.
The team were cold calling and updating, and when a job was identified, a search was made of the people available.
The way I handled it was to have two menu buttons.
Button 1 automatically saved and closed the current form, launched the search facility as read only.
Button 2 closed the search and opened the record you were previously working on.