3523 .... lots of issues

[martinwcole]

Re: 3523 .... lots of issues

since we are looking at getting a new server, 2008 64 Bit, this is an issue I am interested in. But in my scenario, there are no workstations - we only use T/S. So hope it is not an issue for us.

[Jeff Fried]

Re: 3523 .... lots of issues

yes my machine for now... but some clients have the 64 bit machines worked into their networks...

When the stall happens what does task manager show?

I don't know the answer to that. I have no way to test it myself so would need to have two people at that end pounding the keys. I assume you're saying to do a ctrl-alt-delete while the stalled computer is waiting. It may show "not responding" temporarily, but I don't know for sure. The computer eventually comes back, but it slowed down tremendously and certainly would not be viable for going live.

I'm going to call Microsoft to see what they have to say about licensing back from 64 to 32 bit. I wonder if they're simply going to say to go out and buy new Windows 7 32-bit licenses.

Jeff

[Al Buchholz]

Re: 3523 .... lots of issues

Can you verify that you are talking about only one 64-bit computer doing processing and not a shared environment? Thanks.

Jeff

yes my machine for now... but some clients have the 64 bit machines worked into their networks...

When the stall happens what does task manager show?

[Jeff Fried]

Re: 3523 .... lots of issues

Jeff

I'm running a5v10 on a win 7 64 bit machine 64 OS (i5? processor..) without issues.... and hammering it pretty hard... not saying there aren't problems some where..

Al,

You may be running your Win 7 64 bit machine as the only one processing, though you're doing a lot with it. My situation relates to more than one computer working in an order entry environment with plenty of choices on pop-up lists, field rules active for fields, etc. When only one of these computers is being used, no problem (though it could be faster). When two computers are actively trying to add orders, total stall. I am thinking 64 bit is the issue but need to figure out a way to prove it. Problem is, they only have 64-bit Windows 7 on the new computers.

Can you verify that you are talking about only one 64-bit computer doing processing and not a shared environment? Thanks.

Jeff

[forskare]

Re: 3523 .... lots of issues

32 bit mode is the only option now...

But the 32 bit mode runs well for me on a 64 bit machine.

I'm not in a hurry to get Alpha 64 bit mode today - maybe tomorrow..

Hi Al,

Yes, I know. I was just musing a couple of food for thought questions.

kenn

[Al Buchholz]

Re: 3523 .... lots of issues

And what if you had 64 bit choice would you still use 32 bit?
I think you are forced to use 32 bit now.


Ken

32 bit mode is the only option now...

But the 32 bit mode runs well for me on a 64 bit machine.

I'm not in a hurry to get Alpha 64 bit mode today - maybe tomorrow..

[kkfin]

Re: 3523 .... lots of issues

Jeff

I'm running a5v10 on a win 7 64 bit machine 64 OS (i5? processor..) without issues.... and hammering it pretty hard... not saying there aren't problems some where..

And what if you had 64 bit choice would you still use 32 bit?
I think you are forced to use 32 bit now.


Ken

[forskare]

Re: 3523 .... lots of issues

This is a known issue:

Running some 32 bit applications on a 64 bit OS could actually be slower. The additional overheads in running 32 bit software in 64 bit mode could cause a slight degradation in performance.

Maybe Alpha is in this category.

This is not a new opinion from me:

We need 64 bit version from Alpha.
We certainly need 64 bit version from WAS

32 bit will soon be outdated system in every aspect. Next Alpha must be 64 bit. I don't get it why we are here still waiting? Where is Alphas Roadmap for 64 bit systems?

Question: Why to even drive 32 bit software in 64 bit system.
Answer: Because 64 bit version is not available.

Question: Do you buy a 32 bit program to a 64 bit system
Answer: Certainly not if I have a 64 bit choice.


Ken

A couple of thoughts/questions: if Alpha comes out with a 64 bit apps, Since most clients have 32 bit machines:

1. Should we should use both 32 and 64 bit machines in order to
deliver a 32 bit or a 64 bit app?
2. Should it require licenses for both 32 bit and 64 bit?

kenn

[Al Buchholz]

Re: 3523 .... lots of issues

Wow! This can be a significant reason for the issues we are encountering. All the machines are 64 bit, and slowness, and even freezing, is the main issue. I wonder if there is a downgrade to 32-bit Windows 7.

Jeff

Jeff

I'm running a5v10 on a win 7 64 bit machine 64 OS (i5? processor..) without issues.... and hammering it pretty hard... not saying there aren't problems some where..

[Jeff Fried]

Re: 3523 .... lots of issues

Wow! This can be a significant reason for the issues we are encountering. All the machines are 64 bit, and slowness, and even freezing, is the main issue. I wonder if there is a downgrade to 32-bit Windows 7.

Jeff

[kkfin]

Re: 3523 .... lots of issues

This is a known issue:

Running some 32 bit applications on a 64 bit OS could actually be slower. The additional overheads in running 32 bit software in 64 bit mode could cause a slight degradation in performance.

Maybe Alpha is in this category.

This is not a new opinion from me:

We need 64 bit version from Alpha.
We certainly need 64 bit version from WAS

32 bit will soon be outdated system in every aspect. Next Alpha must be 64 bit. I don't get it why we are here still waiting? Where is Alphas Roadmap for 64 bit systems?

Question: Why to even drive 32 bit software in 64 bit system.
Answer: Because 64 bit version is not available.

Question: Do you buy a 32 bit program to a 64 bit system
Answer: Certainly not if I have a 64 bit choice.


Ken

[martinwcole]

Re: 3523 .... lots of issues

Using the 3539, so far I have come accross 2 issues I have successfullu coded around

1. Events, like cansaverecord event in field rules, firing multiple times: fix, using the global logical busy

if busy
     end
end if 
busy=.t.
'put cansaverecord code here
busy=.f. 'reset it

2. In the cansaverecord event in field rules, for many years I have used code like this to silently prevent blank records in embedded browses (that is not currently working correctly):

t=table.current() ' or t=table.get("dailyentries")
if t.fieldone="" .and. t.fieldtwo="" '(two fields are blank)
     cancel()
     end
end if

here is the current work-a-round that is working:

t=table.current() ' or t=table.get("dailyentries")
if t.fieldone="" .and. t.fieldtwo="" '(two fields are blank)
     if is_object("dailyentries")
          :dailyentries:browse1.cancel()
     end if 
     end
end if

[Jeff Fried]

Re: 3523 .... lots of issues

Jeff,

Thanks for the info. We're about to test the patch just prior to 2725_3520, which is 2659_3515. If that doesn't work well, I'll just try your suggestion next.

Jeff

[jkletrovets]

Re: 3523 .... lots of issues

Just as point of reference.....I was on record as saying I was not having problems with 3523 and above in this thread.....further testing proved that to be a FALSE statement. 3539 was causing me issues as well. I reverted to 3520 and my issues went away.

The issues I was having were related to data not being saved properly in embedded browses.

Hopefully, Alpha will get some of this resolved soon....I have seen mention that one user got a special patch(after 3539) after submitting a bug report - which Selwyn is great at providing - that has solved his issues. So, maybe there is hope.

The issue I am having is that my current app is a hybrid and I have to constantly switch between 3539 to make the web side work and then rollback to 3520 to work on the desktop side....


Regards,

Jeff

[Jeff Fried]

Re: 3523 .... lots of issues

I'm a latecomer to this thread but have related issues to what has been discussed.

I found that the current release, 2814_3539, has significant issues. Most prominent is the inability to add a record in a region. This is running under 64-bit Windows 7.

I backed down to the previous release, 2787_3538, and that problem was gone but new problems arose, such as freeze-ups or delays while multiple users (only two for the test) are hitting the file.

I have not yet, but will try, the suggested 2659_3515 to see if it will function, but when I look at the 36 releases to date for A5V10, I wonder where in this group is the most stable one to use. My irate client is wondering why all the equipment upgrades and move to Windows 7 and upgrade to A5V10 has resulted in a degradation of performance to the point where it is unusable. They have been performing perfectly well with old computers running with A5V7 under Windows XP, and now they can't turn back. Luckily they are still working with the old system and the old equipment. Each desktop has an old and new computer with an old and new set of software, and they just can't go live with the new until I find a way to make V10 work for them.

I wonder if there are that many obstacles to designing a stable V10 under Windows 7 64-bit. I realize that V10 is packed with great additional functionality, but when will it plateau to a reasonable degree of stability and speed?

Perhaps the web apps don't have these issues, understandably. But this is strictly a desktop application, and that's what counts right now.

Jeff