Date   

Re: Magic XPA 3.3b and MSSQL Very Slow

DarKWateR
 

Sorry!
When i said "without transaction", i only meant "No Transaction at XPA Task" (implicit in database)

The difference between xpa 3.3a in my case is (always talking from xpa, not database):
Xpa 3.3a Works ok with and without transaction in batch task.
Xpa 3.3b only works ok with transaction active in batch task. With transaction to No, is very very very very slow.


Re: Magic XPA 3.3b and MSSQL Very Slow

Andreas Sedlmeier
 

Hi Darkwater,

Its not possible to work without transactions in MSSQL (actually not possible with any DBMS besides maybe Informix). If you do not work with explicit transactions, it will be implicit transactions - every single statement is wrapped in a transaction (autocommit).

What is the isolation mode you work with. I can imagine that you worked with 0 (dirty read) in the past and now default is 1 (committed read). Dirty read you better avoid, you can however work with snapshot isolation in MSSQL and that should bring back some performance. Try with READ COMMITED and enable snapshot isolation: https://docs.microsoft.com/en-ie/dotnet/framework/data/adonet/sql/snapshot-isolation-in-sql-server for the database

Thats not a real committed then, MSSQL behaves then like Oracle does by default since ever.

Best regards,

Andreas


Re: Magic xpa2.3a

russell_cunha@...
 

Andy

Thank you 

Regards


Re: Enlarging Group-control without linked fields moving [XPA3]

Wes Hein
 

Florian,

Click on the group, all the controls should be highlighted, Ctrl-Click on the group to de-select it.

Wes


Re: Magic xpa2.3a

Andy Jerison
 

You can fix this from the keyboard:
1) Shift focus to the (invisible) window. Ctrl+E will do it in this case.
2) Press Alt+Space. The window's context menu will appear.
3) Press M or click "Move".
4) Move the mouse. You can move the window to the active desktop with the mouse or, once movement is initiated, with the arrow keys.
5) Press Enter when done.

Andy

On Mon, Dec 3, 2018 at 10:19 AM russell_cunha via Groups.Io <russell_cunha=yahoo.com@groups.io> wrote:
Thanks Gabor

Windows multiple displays (monitors) at work. I was using multiple monitore last night while programming the expression table was displaying on one monitor while the  logical view was on another. I packed up my laptop this morning and went to another location and did not think of resetting the displays.

The solution was to plugin another display and let the expression rules display on a second monitor, drag to over to my laptop monitor and it was regularized.

I wonder if there is a hot key to fix this?

Thanks anyway


Re: Magic xpa2.3a

russell_cunha@...
 

Thanks Gabor

Windows multiple displays (monitors) at work. I was using multiple monitore last night while programming the expression table was displaying on one monitor while the  logical view was on another. I packed up my laptop this morning and went to another location and did not think of resetting the displays.

The solution was to plugin another display and let the expression rules display on a second monitor, drag to over to my laptop monitor and it was regularized.

I wonder if there is a hot key to fix this?

Thanks anyway


Enlarging Group-control without linked fields moving [XPA3]

Florian Groothuis
 

Hi,

 

I wonder if there is a way to get this properly working. It worked fine, until XPA with the .NET form editor came along.

 

I have this situation:

A online screen with around 30 fields on it, have of them are linked to a Group-control
.

I need more space at the top in that group, so I select the group and drag it from the top up. But all linked fields are moving upward with my drag. So all the space I create is situated at the bottom. To get the space at the top I have to move the fields down. But, there is no way to select ONLY the fields within the group other than shift+click all of them. Dragging a selection doesn’t work, CTRL+A also selects all the fields outside the group. I tried all possible combinations, dragging and clicking, with shift, ctrl, alt.

 

Is there a normal way to achieve this that without spending a lot of time clicking separate fields?


Re: Magic xpa2.3a

Gábor Bor
 

Hy Russel,

If it's possible, an upgrade to next 2.3X may help. (helps to me in 3.x)

Best regards,
Gábor


Magic xpa2.3a

russell_cunha@...
 

Hello Magicians

Suddenly Expression Rules not displaying when zoomed to from within data view range expression. Any answers will be appreciated.

Regards

Russell 


Re: mgent1 and xpa 3.x behavior

Ramon de Wit
 

Chris,

 

 

WEIRD, but it did the trick!

 

Is this a bug? It seems this behavior started from version 3.x.

 

 

Thanks!

 

 

Van: c.debijl@... [mailto:c.debijl@...]
Verzonden: maandag 3 december 2018 11:52
Aan: Ramon de Wit
Onderwerp: Re: [magicu-l] mgent1 and xpa 3.x behavior

 

Ramon,
I use seperate license files for ria and mgent1 licenses.
Maybe this solution solves your problem too.

Chris

Op 3 dec. 2018 11:01 schreef Ramon de Wit <rwit@...>:

Hello,

 

 

 

For many years we have a ‘mgent1’ to serve web requests for our websites and a ‘mgria’ for our RIA application / Mobile app.

 

These are very old license types, I think that years ago something’s changed that RIA and mobile became separate or so? I’m not sure.

 

Anyhow, this is how it looked under XPA 2.x which is fine:

 

 

 

We are now migrating to a new server and XPA 3.x and now we are using the 3.x version of the same licenses.

 

However the MGENT1 now looks ‘weird’. It looks like it’s representing as a RIA kind of license? Also after a while it terminates itself because of a license error.

 

 

I’m using almost the exact same INI’s.

 

Is there a behavior change regarding this in XPA 3.x, or did I simply make a configuration error somewhere?

 

 

 

Ramon

 

 

 

 

 

Met vriendelijke groet,

 

 

 

Ramon de Wit

Mage - Magic Engineering

Postbus 36170

1020 MD Amsterdam

+31 (0)20 - 6325446

 


Re: Magic XPA 3.3b and MSSQL Very Slow

DarKWateR
 

Original Task, read and write in temporal, butfor this tests i configure table in read mode, and task in query mode - End No - Condition: Before.

Thanks for your reply!


Magic XPI - 4.7 : : Build Failed

Kumbhar, Sunil
 

Dear All,
We have upgraded our project from iBolt 3.2 sp1b to Magic XPI 4.7.  After upgrading project , we have loaded it on TFS server for multi-user development. We have @15 flows in this project. To work step by step, we Initially made most of the flows inactive and few are active. When I build solution or build project, it shows 0 errors , 1 warning and 603 Info messages and says Build failed.
I checked log file (Magicxpi47\Studio\Log\MagicXPI.LOG) but did not found any error in it. Can someone help me to find out exact error for build failed.

Thanks and Regards,
Sunil Kumbhar


Re: Magic XPA 3.3b and MSSQL Very Slow

Gábor Bor
 

Hy DarKwateR,

Do you write it, or only read from the table? (No Before Batch)


mgent1 and xpa 3.x behavior

Ramon de Wit
 

Hello,

 

 

 

For many years we have a ‘mgent1’ to serve web requests for our websites and a ‘mgria’ for our RIA application / Mobile app.

 

These are very old license types, I think that years ago something’s changed that RIA and mobile became separate or so? I’m not sure.

 

Anyhow, this is how it looked under XPA 2.x which is fine:

 

 

 

We are now migrating to a new server and XPA 3.x and now we are using the 3.x version of the same licenses.

 

However the MGENT1 now looks ‘weird’. It looks like it’s representing as a RIA kind of license? Also after a while it terminates itself because of a license error.

 

 

I’m using almost the exact same INI’s.

 

Is there a behavior change regarding this in XPA 3.x, or did I simply make a configuration error somewhere?

 

 

 

Ramon

 

 

 

 

 

Met vriendelijke groet,

 

 

magelogo_v3_smalll

 

Ramon de Wit

Mage - Magic Engineering

Postbus 36170

1020 MD Amsterdam

+31 (0)20 - 6325446

 


Magic XPA 3.3b and MSSQL Very Slow

DarKWateR
 

Hi, I'm testing version 3.3B in my environment and the result is extremely slow.
I installed OLE DB Driver version 18, as the reléase notes says.

I tried a very simple task.
A Batch task that traverses a complete table without a transaction.
The result is about 17 seconds for about 30000 records.
The task does not use transaction.

If you enable the transaction at the "Task Prefix " Level, it takes only about a second / two seconds, for the same number of records.
Does anyone have any idea if there is any configuration option that solves this problem without having to enable transactions where they are not needed?
Greetings and thank you very much and I feel my English.


Re: Printing over RDP

Andreas Sedlmeier
 

Hi Arch,

When that default printer is a local printer, then everything seems to be installed and configured fine, just the (long) printer name is obviously a problem for Magic.

To be sure about the installation check the event log of the server re printer related messages (https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc727392(v=ws.10))

For a test you can simply open Print Management in your remote desktop and rename the printer name there to "Sticker" and try with that name in Magic appliaction.

Best regards,

Andreas


Re: Printing over RDP

Keith Canniff
 

Arch,

 

Normally each printer is assigned a static IP on the network LAN/WAN. The print server is also defined with a static IP and a server name.

 

Not sure how their network is configured, but with the above, it’s just like we stated:

 

\\Servername\PrinterName

 

Nothing more complicated and the above resides in the INI file.

 

Keith

 

From: main@magicu-l.groups.io <main@magicu-l.groups.io> On Behalf Of Arch
Sent: Friday, November 30, 2018 3:01 PM
To: Magic Group <main@magicu-l.groups.io>
Subject: Re: [magicu-l] Printing over RDP

 

Sounds like both Sherm and Keith are talking about the same solution - and it makes sense. How about this?

 

1) assign a static IP to the printer computer in TX

2) forward port yyyy to the TX computers static IP from their router.

3) install printer drivers in Hickory for each printer assigning them to port //xxx.xxx.xxx.xxx:yyyy/PrinterName

4) Assign the [Magic_Printers] entries using the PrinterName

 

Think that will work?

 

Arch Lineberger

203 N Main St

Belmont, NC 28012

704.461.1223

 

 

On Fri, Nov 30, 2018 at 2:07 PM sherman levine <slevine@...> wrote:

Arch,

If Magic can't handle names for the workstation's printers (the ones which have "redirected" in their name ) then you can ask the people in Hickory to install the same physical printers on their RDP server or on their print server (or even on a print server in Texas).
That way the RDP server can access them using \\servername\printername  which will be fine for Magic.

Sherm

On 11/30/2018 01:59 PM, Arch wrote:

Sherm,

 

I am not sure what you mean by "hosting" a printer on the server. 

 

The TX(client) printer appears in the Windows Settings/Devices/Printers dialog box on the Hickory server and I can print a test page from the server on the client printer using RDP from the client. What I cannot do is get my Magic application running on the server to print to the correct client printer - it always prints to the client's Default printer.

 

Arch Lineberger

203 N Main St

Belmont, NC 28012

704.461.1223

 

 

On Fri, Nov 30, 2018 at 1:53 PM sherman levine <slevine@...> wrote:

You were clear. Is there a reason why the Hickory print server can't host a printer which is physically located in Texas.

I have clients who do that - One central Magic installation, Terminals control the server via RDP, and one print server handles all the remote warehouse printing.

Sherm

On 11/30/2018 01:46 PM, Arch wrote:

I must not have been clear... The forms must be printed in TX. 

  • The printers in TX appear on the Hickory computer as redirected through RDP - there is no driver issue. 
  • I can print test pages on the TX computer from the Hickory computer using RDP from TX to Hickory.
  • What I can't deem to do is get the Magic application running in Hickory to address their output to the specific TX printers - they all go to the TX Default printer.

 

Arch Lineberger

203 N Main St

Belmont, NC 28012

704.461.1223

 

 

On Fri, Nov 30, 2018 at 12:41 PM sherman levine <slevine@...> wrote:

Why not ask Hickory to install the two Texas printers on their print server?


On 11/30/2018 12:10 PM, Arch wrote:

A plant in Hickory is acting as an RDP server for a plant in Texas. The TX computer has 2 printers installed that are named Sticker and Ticket. TX is running RDP to the Hickory computer to run the Magic application and print labels on the two TX printers.

 

From the point of view of the Hickory computer, the TX printers are seen as Sticker (redirected 7) and Ticket (redirected 7). How do I get the application, running in Hickory to print to the TX printers?

 

I have tried setting the Magic printers to Sticker and Ticket and selected them in the program's IO Properties. The output goes to the TX default printer. Then I tried setting them to "Sticker (redirecte" and "Ticket (redirected" which are the maximum characters available in the Options/Settings/Printers dialog. Still, output goes to the TX default printer.

 

What am I doing wrong? Can this work over Windows 10 RDP?

 

Arch Lineberger

203 N Main St

Belmont, NC 28012

704.461.1223

 

 

 


Virus-free. www.avast.com


Re: Printing over RDP

Arch <Arch.Lineberger@...>
 

Sounds like both Sherm and Keith are talking about the same solution - and it makes sense. How about this?

1) assign a static IP to the printer computer in TX
2) forward port yyyy to the TX computers static IP from their router.
3) install printer drivers in Hickory for each printer assigning them to port //xxx.xxx.xxx.xxx:yyyy/PrinterName
4) Assign the [Magic_Printers] entries using the PrinterName

Think that will work?

Arch Lineberger
203 N Main St
Belmont, NC 28012
704.461.1223


On Fri, Nov 30, 2018 at 2:07 PM sherman levine <slevine@...> wrote:
Arch,

If Magic can't handle names for the workstation's printers (the ones which have "redirected" in their name ) then you can ask the people in Hickory to install the same physical printers on their RDP server or on their print server (or even on a print server in Texas).
That way the RDP server can access them using \\servername\printername  which will be fine for Magic.

Sherm

On 11/30/2018 01:59 PM, Arch wrote:
Sherm,

I am not sure what you mean by "hosting" a printer on the server. 

The TX(client) printer appears in the Windows Settings/Devices/Printers dialog box on the Hickory server and I can print a test page from the server on the client printer using RDP from the client. What I cannot do is get my Magic application running on the server to print to the correct client printer - it always prints to the client's Default printer.

Arch Lineberger
203 N Main St
Belmont, NC 28012
704.461.1223


On Fri, Nov 30, 2018 at 1:53 PM sherman levine <slevine@...> wrote:

You were clear. Is there a reason why the Hickory print server can't host a printer which is physically located in Texas.

I have clients who do that - One central Magic installation, Terminals control the server via RDP, and one print server handles all the remote warehouse printing.

Sherm

On 11/30/2018 01:46 PM, Arch wrote:
I must not have been clear... The forms must be printed in TX. 
  • The printers in TX appear on the Hickory computer as redirected through RDP - there is no driver issue. 
  • I can print test pages on the TX computer from the Hickory computer using RDP from TX to Hickory.
  • What I can't deem to do is get the Magic application running in Hickory to address their output to the specific TX printers - they all go to the TX Default printer.

Arch Lineberger
203 N Main St
Belmont, NC 28012
704.461.1223


On Fri, Nov 30, 2018 at 12:41 PM sherman levine <slevine@...> wrote:
Why not ask Hickory to install the two Texas printers on their print server?


On 11/30/2018 12:10 PM, Arch wrote:
A plant in Hickory is acting as an RDP server for a plant in Texas. The TX computer has 2 printers installed that are named Sticker and Ticket. TX is running RDP to the Hickory computer to run the Magic application and print labels on the two TX printers.

From the point of view of the Hickory computer, the TX printers are seen as Sticker (redirected 7) and Ticket (redirected 7). How do I get the application, running in Hickory to print to the TX printers?

I have tried setting the Magic printers to Sticker and Ticket and selected them in the program's IO Properties. The output goes to the TX default printer. Then I tried setting them to "Sticker (redirecte" and "Ticket (redirected" which are the maximum characters available in the Options/Settings/Printers dialog. Still, output goes to the TX default printer.

What am I doing wrong? Can this work over Windows 10 RDP?

Arch Lineberger
203 N Main St
Belmont, NC 28012
704.461.1223





Re: Printing over RDP

sherman levine
 

Arch,

If Magic can't handle names for the workstation's printers (the ones which have "redirected" in their name ) then you can ask the people in Hickory to install the same physical printers on their RDP server or on their print server (or even on a print server in Texas).
That way the RDP server can access them using \\servername\printername  which will be fine for Magic.

Sherm

On 11/30/2018 01:59 PM, Arch wrote:
Sherm,

I am not sure what you mean by "hosting" a printer on the server. 

The TX(client) printer appears in the Windows Settings/Devices/Printers dialog box on the Hickory server and I can print a test page from the server on the client printer using RDP from the client. What I cannot do is get my Magic application running on the server to print to the correct client printer - it always prints to the client's Default printer.

Arch Lineberger
203 N Main St
Belmont, NC 28012
704.461.1223


On Fri, Nov 30, 2018 at 1:53 PM sherman levine <slevine@...> wrote:

You were clear. Is there a reason why the Hickory print server can't host a printer which is physically located in Texas.

I have clients who do that - One central Magic installation, Terminals control the server via RDP, and one print server handles all the remote warehouse printing.

Sherm

On 11/30/2018 01:46 PM, Arch wrote:
I must not have been clear... The forms must be printed in TX. 
  • The printers in TX appear on the Hickory computer as redirected through RDP - there is no driver issue. 
  • I can print test pages on the TX computer from the Hickory computer using RDP from TX to Hickory.
  • What I can't deem to do is get the Magic application running in Hickory to address their output to the specific TX printers - they all go to the TX Default printer.

Arch Lineberger
203 N Main St
Belmont, NC 28012
704.461.1223


On Fri, Nov 30, 2018 at 12:41 PM sherman levine <slevine@...> wrote:
Why not ask Hickory to install the two Texas printers on their print server?


On 11/30/2018 12:10 PM, Arch wrote:
A plant in Hickory is acting as an RDP server for a plant in Texas. The TX computer has 2 printers installed that are named Sticker and Ticket. TX is running RDP to the Hickory computer to run the Magic application and print labels on the two TX printers.

From the point of view of the Hickory computer, the TX printers are seen as Sticker (redirected 7) and Ticket (redirected 7). How do I get the application, running in Hickory to print to the TX printers?

I have tried setting the Magic printers to Sticker and Ticket and selected them in the program's IO Properties. The output goes to the TX default printer. Then I tried setting them to "Sticker (redirecte" and "Ticket (redirected" which are the maximum characters available in the Options/Settings/Printers dialog. Still, output goes to the TX default printer.

What am I doing wrong? Can this work over Windows 10 RDP?

Arch Lineberger
203 N Main St
Belmont, NC 28012
704.461.1223





Re: Printing over RDP

Keith Canniff
 

Arch,

 

As long as they are not session printers and just other named printers on the network

 

Are you using the following syntax in your MAGIC_PRINTERS section

 

<print server name>\printername

 

Example

 

[MAGIC_PRINTERS]

Ticket = *\\TXPrntSrv1\<IP or Printer name for Ticket Printer>

Sticker = *\\TXPrntSrv1\<IP or Printer name for Sticker Printer>

 

Keith

 

From: main@magicu-l.groups.io <main@magicu-l.groups.io> On Behalf Of Arch
Sent: Friday, November 30, 2018 1:46 PM
To: Magic Group <main@magicu-l.groups.io>
Subject: Re: [magicu-l] Printing over RDP

 

I must not have been clear... The forms must be printed in TX. 

  • The printers in TX appear on the Hickory computer as redirected through RDP - there is no driver issue. 
  • I can print test pages on the TX computer from the Hickory computer using RDP from TX to Hickory.
  • What I can't deem to do is get the Magic application running in Hickory to address their output to the specific TX printers - they all go to the TX Default printer.

 

Arch Lineberger

203 N Main St

Belmont, NC 28012

704.461.1223

 

 

On Fri, Nov 30, 2018 at 12:41 PM sherman levine <slevine@...> wrote:

Why not ask Hickory to install the two Texas printers on their print server?


On 11/30/2018 12:10 PM, Arch wrote:

A plant in Hickory is acting as an RDP server for a plant in Texas. The TX computer has 2 printers installed that are named Sticker and Ticket. TX is running RDP to the Hickory computer to run the Magic application and print labels on the two TX printers.

 

From the point of view of the Hickory computer, the TX printers are seen as Sticker (redirected 7) and Ticket (redirected 7). How do I get the application, running in Hickory to print to the TX printers?

 

I have tried setting the Magic printers to Sticker and Ticket and selected them in the program's IO Properties. The output goes to the TX default printer. Then I tried setting them to "Sticker (redirecte" and "Ticket (redirected" which are the maximum characters available in the Options/Settings/Printers dialog. Still, output goes to the TX default printer.

 

What am I doing wrong? Can this work over Windows 10 RDP?

 

Arch Lineberger

203 N Main St

Belmont, NC 28012

704.461.1223

 


Virus-free. www.avast.com

6741 - 6760 of 195968