Slooooooowwww opening of a form

[Jure Zorko]

I have come across a strange problem.

I have problem with only one form. I changed one line of code on this form. Nothing special. 

...

TC."something" = read from INI

...

But I thing this line is not a problem. Because:

If I save this form and then open this form on customers computer, form opens sloooooowwwwwlllllly. Aprox 5 minutes.

BUT if I open in design and save (no changes) this form on customers computer, everything works as expected.

AND if I open this newly saved form back on my computer and re-save it, then this form on customers computer is slooooow again.

Interesting part: this happens only with one form and only with one customer.

To recap: If I save form on my computer, it works at all customers but one.

If I save form on that customers computer, it works at all customers.

Any ideas?

I think it has to do something with paradox installation, but have no idea, where to look.

Thx Jure

[Kevin Zawicki]

You are running source code (fsl) not (fdl), correct?

It sounds maybe like a compile issue which may be related to Paradox version. What specific version are in use?

In the slow scenario, have you used breakpoint or trace to see where is hangs?

Is the INI file located in same place relative to the form? Is it on a network? C: drive?

Can you temporarily replace "read from INI" with a hard coded variable to see if the INI read is the problem?

[TheDBCommunity]

I have vague memories of this.  Something to do with the style sheet, possibly.  Is the style sheet on the client computer?  Is it at the same path as on the developer computer?

Liz

[Kevin Zawicki]

Yes, style sheets cause odd issues, the resave and works might indicate the "refresh" of the style sheet on compile.

[TheDBCommunity]

Also, while searching pnews, I was reminded that antivirus software exists... :D  Jure, make sure the client machine isn't letting the AV scan Paradox files.  Will let you know if I find anything else.

Liz

[TheDBCommunity]

If opening the form via code, make sure to include the file extension.  Otherwise, AV and style sheet look like the most likely issues.  Search ended.

Liz

[Jure Zorko]

So:

* I use FSL (because most customers have P9, some are still on P7, a couple of them are on P11, because P9 would not install ????? )

* I do not have FDL in folder.

* customers use runtime. Latest versions. SP3. BDE is 5.2.0.2

* Style sheets: I do not use them, this is actually the FIRST time I even opened menu Format-Style sheet.  On both computers list is empty.

* breakpoints: first time I traced the code, it "stopped" on a sleep() command in library. I removed call to this library, then it "stopped" on readprofilestring(). When I removed this readprofile, it "stopped" on some later line. FSL is NOT over 1Mb limit.

* It only happens on ONE form at ONE customer. I have over 600 forms and 200 customers, and none of the others behaves like this.

Jure

[TheDBCommunity]

Intentionally or not, you do use style sheets.  Paradox will use a default if you don't specify one.  It's not possible not to.  In dev, do you save this form in P7 before delivering to all the customers?  I'd worry the P7 instance wouldn't open a P11 form, for example, whereas P11 should open a P7 form...

It may be inconvenient for you, but the best thing you can do is to compile the form in each version and deliver the FDL to customers.

What version of Paradox is the problem customer using, and what version are you using in dev?

Back to style sheets:

WARNING: Do not change style sheets - doing so can redesign all the objects on the form to match the new style sheet.  Make a backup before playing around.

In Paradox, without anything else open, go to Tools > Settings > Preferences; Forms / Reports tab.  Look at the bottom.  Are the "Designer style sheets:" fields populated?  If not, IMO, you have an installation or configuration problem.  The style sheets should be in the install directory, in a pdoxhome subdir.  For example, the default install for P11 puts them here:

C:\Program Files (x86)\Corel\Paradox\Paradox\pdoxhome

DEFAULT.FP is the default for reports and DEFAULT.FT is the default for forms.  If you copy these files from your dev machine, and put them into the same path (even if you must create the path) on your client machine, that may resolve the problem.

There are objectPAL methods for style sheets - getStyleSheet, setStyleSheet, saveStyleSheet.  You could potentially use these in dev to create a .FT file to place on all your client computers, but they have to be in the dir where the form thinks its style sheet lives.

If none of that works, then we probably need to know a lot more about the differences between this form and other forms (including when it was created, comparatively; and what Paradox objects and features it uses that may differ from other forms; data model complexity; unique tables or indexes used) and how the client's environment (OS, Paradox version, networking, etc.) differs from dev / everyone else.

Do any other customers use this form?

FWIW,

Liz

[Jure Zorko]

Hmmm, on both computers I have PXTOOLS.FT  in both fields and that is the only option in dropdown.

I can not find PXTOOLS.FT anywhere on disk ????

Did I install something a long time ago and don't remember (PxTools? Is that something to install?)?

Looks like I need to do some reinstalling.

Jure

[TheDBCommunity]

Huh.  Maybe a custom style sheet included with something one of us made that you downloaded?  Anywho, your problem may be solved simply by putting that FT file into the same path on the client's computer.  Hard to say.

Much as I hate to suggest it, forms can become corrupted, and it could be that you need to make a new form from scratch - don't copy and paste objects, but you can copy and paste code.  If nothing else resolves this issue, this could.

Good luck! :)

Liz