|
Roman Goldenberg
Hi,
A solution for us was to stop windows defender for first time ria application opening and after that to start defender back. Also we checked mgxparia.exe for trojan and it was safety,
|
||
|
|
||
|
Tim Downie
Ive been here
You just need to go into windows where its seen as a threat , and say ignore this. There appears to be no way to be able to just say ignore this exe in a list.
It needs to be seen a a threat first
In windows security center - look under Virus & Threat protection , then under Scan history , if you have detected threats they are here - find the ria.exe and go ignore.
(BTW : you have no idea how long it took to find the screen i mention above).
What i dont get , we have a lot of RIA users very few see it this problem , from what i can see i can have two machines with all windows updates and one has the issues and the other doesnt
From: main@magicu-l.groups.io <main@magicu-l.groups.io> on behalf of Darren <darren.jimenez@...>
Sent: Wednesday, 4 September 2019 2:28 AM To: main@magicu-l.groups.io <main@magicu-l.groups.io> Subject: [magicu-l] Cannot Open RIA app via ClickOnce on some client's PC, Issue with Windows 10 1903 Windows Defender. #ria #xpa Hello Everyone, A number of users reported that they clicked Start and nothing was happening, so I tried to remote one of the users and checked task manager what is happening. I found out that the application opens for 1-2 seconds and closes again. I had to confirm with MSE what was happening and I was informed that windows defender update flags the application as a trojan. For now we are disabling windows defender real time protection for the affected users so that they can use our application and for them to be able to proceed with their work.
For now MSE is working on a permanent solution, but for the mean time, do you have any other ideas rather than disabling real-time protection? Best Regards, Darren
|
||
|
|
||
|
Darren
Hello Everyone, A number of users reported that they clicked Start and nothing was happening, so I tried to remote one of the users and checked task manager what is happening. I found out that the application opens for 1-2 seconds and closes again. I had to confirm with MSE what was happening and I was informed that windows defender update flags the application as a trojan. For now we are disabling windows defender real time protection for the affected users so that they can use our application and for them to be able to proceed with their work.
For now MSE is working on a permanent solution, but for the mean time, do you have any other ideas rather than disabling real-time protection? Best Regards, Darren
|
||
|
|
||
|
Re: Default VC server
Roman Goldenberg
Hi Florian,
do you install version control provider on work station? magic required version control provider to connect to VC-Server. after installation if you have several client providers please check default source control provider location in registry , magic looking for this location to prompt for the server.
|
||
|
|
||
|
Re: Locate a Record Problem (Nearly Solved)
buster reinke
Thanks Sherm, that simple expression was all that was needed. Now everything is working perfectly. All parameters are working and Locate a Record is also working on all tables now. Much appreciated. Buster
On Tuesday, 3 September 2019, 10:05:26 am AEST, sherman levine <sherman.levine@...> wrote: Buster, In this range expression, one of the first two conditions is always true, so you never get beyond them If(pAircraft Reg= ' ', Aircraft Reg = Aircraft Reg, If(pAircraft Reg <> ' ' ,pAircraft Reg = Aircraft Reg, I think you're looking for something like this as a range expression (pA='' or pA=A) and (pB='' or pB=B) and (pC='' or pC=C) etc Now, particularly if you're working with a SQL database, the better way to accomplish the same thing in Magic is the cndrange() expression For variable A, range is cndrange(pA>'',pA) to cndrange(pA>'',pA) For variable B, range is cndrange(pB>'',pB) to cndrange(pB>'',pB) etc Sherm On 9/2/2019 7:45 PM, buster reinke via Groups.Io wrote: I've found a way around the problem, but it only works for programs with 1 parameter passed on. I removed the Expressions in the From and To fields, and put an expression in the Tasks/Range/Locate Range Expression area instead. I simply used If(pPart Number=' ',Part Number = Part Number, pPart Number = Part Number) This now allows Locating in Tables with or without parameters passed to them. But I have some programs with multiple parameters passed to them and it is only recognising the first part of the expression. I used the following expression: If(pAircraft Reg= ' ', Aircraft Reg = Aircraft Reg, If(pAircraft Reg <> ' ' ,pAircraft Reg = Aircraft Reg, If(pPart Number = ' ' ,Part Number = Part Number, if(pPart Number <> pPart Number = Part Number, If(pSerial Number = ' ' ,Serial Number = Serial Number, if(pSerial Number <> pSerial Number = Serial Number,0)))))) Now the Locate function works, but the passed parameters are being ignored except for the Aircraft Reg part. (This was initially at the end of the expression, and when it didn't work, I moved it to the start of the expression, and it then worked, eg, initially I was getting all Aircraft in the data view, and when I changed the expression, I was able to filter it to the aircraft I want, but for the Part Number ans Serial Number part of the expression, I am still getting everything in the data view. Not all of the parameters are being used all the time, some of them are skipped in the arguments section. I'm sure that it doesn't like my expression format, but I'm not sure how to fix it. If anyone there can understand what I am trying to do here, I would appreciate help that with an expression that will allow all the passed parameters to be filtered as necessary. On Tuesday, 3 September 2019, 7:21:21 am AEST, buster reinke via Groups.Io <buster_png@...> wrote: Further to this, it wasn't my expression causing this. It appears that if any of the files are using passed parameters to it, the locate to function will not work unless the * is placed after the ficure entered into the locte field. Maybe it is a bug after all.....This explains why some of my tables will locate properly, and some wont..... Buster On Tuesday, 3 September 2019, 7:14:23 am AEST, buster reinke via Groups.Io <buster_png@...> wrote: Hi Govert, I've worked out what's causing it, I just now need to find a solution. I have been trying to use the same program files whether they are accessed directly, or if they are using papameters passed to them: So in the range from field, I have used the expression "IF(pPart Number=' ','0',pPart Number" In the range to field, I have used "IF(pPart Number=' ','ZZZZZZZZZZZZZZZZZZZZZZZZZ',pPart Number". This allowed me to get the table to ignore the Parameters if I accessed the table directly, but this is what is interfering with the Locate a Record function. I could just create several files, some with the required parameters, and some without, and link them to the programs that call them, but that means I can't just make any programming changes in the one place if required. Do you know another way I can use the same file, whether passed parameters are used or not? On Tuesday, 3 September 2019, 6:53:33 am AEST, buster reinke via Groups.Io <buster_png@...> wrote: Hi Govert, they are Alpha fields I am trying to locate on. They are all Key Indexes, but I just tried using the * after entering the first digit, and that worked. Buster On Monday, 2 September 2019, 8:59:03 pm AEST, Govert Schipper <govertschipper@...> wrote: Buster, Is the field you are locating on an Alpha field? If it is Numeric, you will have to type the whole value Is the field you are locating on the first or only key segment? If not, you might try to use an * right after your value Govert Van:main@magicu-l.groups.io <main@magicu-l.groups.io> namens buster reinke via Groups.Io<buster_png@...> Verzonden: maandag 2 september 2019 12:31 Aan: main@magicu-l.groups.io<main@magicu-l.groups.io> Onderwerp: Re: [magicu-l] Locate a Record Problem Hi Keith, yes, I have Indexes on the Fields I am trying to search on. They are Alpha Fields. I have just found that if I type in the entire contents of a field eg "2622311-16", it will take me to the record, but if I just type 26 and hit locate, it takes me back to the start. It has me buggered, other Line Tables are working perfectly. Buster On Monday, 2 September 2019, 8:11:00 pm AEST, Keith Canniff <kcanniff@...> wrote: Buster,
Keith
From:main@magicu-l.groups.io <main@magicu-l.groups.io>On Behalf Of buster reinke via Groups.Io
Hello all, I am having a problem with the Locate a Record function for some Tables. Some Line Tables work with no problems. It always takes me to the first record when I enter the first digit, but for other tables, it always takes me back to the 1st record. Some of my Screen tables will Locate a Record providing I am only trying to Locate on the first field. I can't see any differences in the Line Tables that the Locate a Record work on, but I know I must have missed something. Does anyone have any idea what could be causing only some Line Tables to Locate correctly on all fields, and none of the Screen Tables to work correctly?
|
||
|
|
||
|
Re: Locate a Record Problem (Nearly Solved)
sherman levine
Buster,
In this range expression, one of the
first two conditions is always true, so you never get beyond them
If(pAircraft Reg= ' ', Aircraft Reg =
Aircraft Reg, If(pAircraft Reg <> ' ' ,pAircraft Reg =
Aircraft Reg,
I think you're looking for something
like this as a range expression
(pA='' or pA=A) and (pB='' or pB=B) and
(pC='' or pC=C) etc
Now, particularly if you're working
with a SQL database, the better way to accomplish the same thing
in Magic is the cndrange() expression
For variable A, range is
cndrange(pA>'',pA) to cndrange(pA>'',pA)
For variable B, range is
cndrange(pB>'',pB) to cndrange(pB>'',pB)
etc
Sherm
On 9/2/2019 7:45 PM, buster reinke via
Groups.Io wrote:
|
||
|
|
||
|
Re: Locate a Record Problem (Nearly Solved)
buster reinke
I've found a way around the problem, but it only works for programs with 1 parameter passed on. I removed the Expressions in the From and To fields, and put an expression in the Tasks/Range/Locate Range Expression area instead. I simply used If(pPart Number=' ',Part Number = Part Number, pPart Number = Part Number) This now allows Locating in Tables with or without parameters passed to them. But I have some programs with multiple parameters passed to them and it is only recognising the first part of the expression. I used the following expression: If(pAircraft Reg= ' ', Aircraft Reg = Aircraft Reg, If(pAircraft Reg <> ' ' ,pAircraft Reg = Aircraft Reg, If(pPart Number = ' ' ,Part Number = Part Number, if(pPart Number <> pPart Number = Part Number, If(pSerial Number = ' ' ,Serial Number = Serial Number, if(pSerial Number <> pSerial Number = Serial Number,0)))))) Now the Locate function works, but the passed parameters are being ignored except for the Aircraft Reg part. (This was initially at the end of the expression, and when it didn't work, I moved it to the start of the expression, and it then worked, eg, initially I was getting all Aircraft in the data view, and when I changed the expression, I was able to filter it to the aircraft I want, but for the Part Number ans Serial Number part of the expression, I am still getting everything in the data view. Not all of the parameters are being used all the time, some of them are skipped in the arguments section. I'm sure that it doesn't like my expression format, but I'm not sure how to fix it. If anyone there can understand what I am trying to do here, I would appreciate help that with an expression that will allow all the passed parameters to be filtered as necessary.
On Tuesday, 3 September 2019, 7:21:21 am AEST, buster reinke via Groups.Io <buster_png@...> wrote: Further to this, it wasn't my expression causing this. It appears that if any of the files are using passed parameters to it, the locate to function will not work unless the * is placed after the ficure entered into the locte field. Maybe it is a bug after all.....This explains why some of my tables will locate properly, and some wont..... Buster On Tuesday, 3 September 2019, 7:14:23 am AEST, buster reinke via Groups.Io <buster_png@...> wrote: Hi Govert, I've worked out what's causing it, I just now need to find a solution. I have been trying to use the same program files whether they are accessed directly, or if they are using papameters passed to them: So in the range from field, I have used the expression "IF(pPart Number=' ','0',pPart Number" In the range to field, I have used "IF(pPart Number=' ','ZZZZZZZZZZZZZZZZZZZZZZZZZ',pPart Number". This allowed me to get the table to ignore the Parameters if I accessed the table directly, but this is what is interfering with the Locate a Record function. I could just create several files, some with the required parameters, and some without, and link them to the programs that call them, but that means I can't just make any programming changes in the one place if required. Do you know another way I can use the same file, whether passed parameters are used or not? On Tuesday, 3 September 2019, 6:53:33 am AEST, buster reinke via Groups.Io <buster_png@...> wrote: Hi Govert, they are Alpha fields I am trying to locate on. They are all Key Indexes, but I just tried using the * after entering the first digit, and that worked. Buster On Monday, 2 September 2019, 8:59:03 pm AEST, Govert Schipper <govertschipper@...> wrote: Buster, Is the field you are locating on an Alpha field? If it is Numeric, you will have to type the whole value Is the field you are locating on the first or only key segment? If not, you might try to use an * right after your value Govert Van: main@magicu-l.groups.io <main@magicu-l.groups.io> namens buster reinke via Groups.Io <buster_png@...> Verzonden: maandag 2 september 2019 12:31 Aan: main@magicu-l.groups.io <main@magicu-l.groups.io> Onderwerp: Re: [magicu-l] Locate a Record Problem Hi Keith, yes, I have Indexes on the Fields I am trying to search on. They are Alpha Fields. I have just found that if I type in the entire contents of a field eg "2622311-16", it will take me to the record, but if I just type 26 and hit locate, it takes me back to the start. It has me buggered, other Line Tables are working perfectly. Buster On Monday, 2 September 2019, 8:11:00 pm AEST, Keith Canniff <kcanniff@...> wrote: Buster,
Keith
From: main@magicu-l.groups.io <main@magicu-l.groups.io>On Behalf Of buster reinke via Groups.Io
Hello all, I am having a problem with the Locate a Record function for some Tables. Some Line Tables work with no problems. It always takes me to the first record when I enter the first digit, but for other tables, it always takes me back to the 1st record. Some of my Screen tables will Locate a Record providing I am only trying to Locate on the first field. I can't see any differences in the Line Tables that the Locate a Record work on, but I know I must have missed something. Does anyone have any idea what could be causing only some Line Tables to Locate correctly on all fields, and none of the Screen Tables to work correctly?
|
||
|
|
||
|
Re: Locate a Record Problem
buster reinke
Further to this, it wasn't my expression causing this. It appears that if any of the files are using passed parameters to it, the locate to function will not work unless the * is placed after the ficure entered into the locte field. Maybe it is a bug after all.....This explains why some of my tables will locate properly, and some wont..... Buster
On Tuesday, 3 September 2019, 7:14:23 am AEST, buster reinke via Groups.Io <buster_png@...> wrote: Hi Govert, I've worked out what's causing it, I just now need to find a solution. I have been trying to use the same program files whether they are accessed directly, or if they are using papameters passed to them: So in the range from field, I have used the expression "IF(pPart Number=' ','0',pPart Number" In the range to field, I have used "IF(pPart Number=' ','ZZZZZZZZZZZZZZZZZZZZZZZZZ',pPart Number". This allowed me to get the table to ignore the Parameters if I accessed the table directly, but this is what is interfering with the Locate a Record function. I could just create several files, some with the required parameters, and some without, and link them to the programs that call them, but that means I can't just make any programming changes in the one place if required. Do you know another way I can use the same file, whether passed parameters are used or not? On Tuesday, 3 September 2019, 6:53:33 am AEST, buster reinke via Groups.Io <buster_png@...> wrote: Hi Govert, they are Alpha fields I am trying to locate on. They are all Key Indexes, but I just tried using the * after entering the first digit, and that worked. Buster On Monday, 2 September 2019, 8:59:03 pm AEST, Govert Schipper <govertschipper@...> wrote: Buster, Is the field you are locating on an Alpha field? If it is Numeric, you will have to type the whole value Is the field you are locating on the first or only key segment? If not, you might try to use an * right after your value Govert Van: main@magicu-l.groups.io <main@magicu-l.groups.io> namens buster reinke via Groups.Io <buster_png@...> Verzonden: maandag 2 september 2019 12:31 Aan: main@magicu-l.groups.io <main@magicu-l.groups.io> Onderwerp: Re: [magicu-l] Locate a Record Problem Hi Keith, yes, I have Indexes on the Fields I am trying to search on. They are Alpha Fields. I have just found that if I type in the entire contents of a field eg "2622311-16", it will take me to the record, but if I just type 26 and hit locate, it takes me back to the start. It has me buggered, other Line Tables are working perfectly. Buster On Monday, 2 September 2019, 8:11:00 pm AEST, Keith Canniff <kcanniff@...> wrote: Buster,
Keith
From: main@magicu-l.groups.io <main@magicu-l.groups.io>On Behalf Of buster reinke via Groups.Io
Hello all, I am having a problem with the Locate a Record function for some Tables. Some Line Tables work with no problems. It always takes me to the first record when I enter the first digit, but for other tables, it always takes me back to the 1st record. Some of my Screen tables will Locate a Record providing I am only trying to Locate on the first field. I can't see any differences in the Line Tables that the Locate a Record work on, but I know I must have missed something. Does anyone have any idea what could be causing only some Line Tables to Locate correctly on all fields, and none of the Screen Tables to work correctly?
|
||
|
|
||
|
Re: Locate a Record Problem
buster reinke
Hi Govert, I've worked out what's causing it, I just now need to find a solution. I have been trying to use the same program files whether they are accessed directly, or if they are using papameters passed to them: So in the range from field, I have used the expression "IF(pPart Number=' ','0',pPart Number" In the range to field, I have used "IF(pPart Number=' ','ZZZZZZZZZZZZZZZZZZZZZZZZZ',pPart Number". This allowed me to get the table to ignore the Parameters if I accessed the table directly, but this is what is interfering with the Locate a Record function. I could just create several files, some with the required parameters, and some without, and link them to the programs that call them, but that means I can't just make any programming changes in the one place if required. Do you know another way I can use the same file, whether passed parameters are used or not?
On Tuesday, 3 September 2019, 6:53:33 am AEST, buster reinke via Groups.Io <buster_png@...> wrote: Hi Govert, they are Alpha fields I am trying to locate on. They are all Key Indexes, but I just tried using the * after entering the first digit, and that worked. Buster On Monday, 2 September 2019, 8:59:03 pm AEST, Govert Schipper <govertschipper@...> wrote: Buster, Is the field you are locating on an Alpha field? If it is Numeric, you will have to type the whole value Is the field you are locating on the first or only key segment? If not, you might try to use an * right after your value Govert Van: main@magicu-l.groups.io <main@magicu-l.groups.io> namens buster reinke via Groups.Io <buster_png@...> Verzonden: maandag 2 september 2019 12:31 Aan: main@magicu-l.groups.io <main@magicu-l.groups.io> Onderwerp: Re: [magicu-l] Locate a Record Problem Hi Keith, yes, I have Indexes on the Fields I am trying to search on. They are Alpha Fields. I have just found that if I type in the entire contents of a field eg "2622311-16", it will take me to the record, but if I just type 26 and hit locate, it takes me back to the start. It has me buggered, other Line Tables are working perfectly. Buster On Monday, 2 September 2019, 8:11:00 pm AEST, Keith Canniff <kcanniff@...> wrote: Buster,
Keith
From: main@magicu-l.groups.io <main@magicu-l.groups.io>On Behalf Of buster reinke via Groups.Io
Hello all, I am having a problem with the Locate a Record function for some Tables. Some Line Tables work with no problems. It always takes me to the first record when I enter the first digit, but for other tables, it always takes me back to the 1st record. Some of my Screen tables will Locate a Record providing I am only trying to Locate on the first field. I can't see any differences in the Line Tables that the Locate a Record work on, but I know I must have missed something. Does anyone have any idea what could be causing only some Line Tables to Locate correctly on all fields, and none of the Screen Tables to work correctly?
|
||
|
|
||
|
Re: Locate a Record Problem
buster reinke
Hello Harry, I don't think it is a bug in Magic, as some of my table allow locating with no problems. Buster
On Monday, 2 September 2019, 9:59:08 pm AEST, <harry@...> wrote: Hi Buster, It's a bug in Magic. You should also fill the until value to get the correct result. Best regards, Harry Kleinsmit.
|
||
|
|
||
|
Re: Locate a Record Problem
buster reinke
Hi Govert, they are Alpha fields I am trying to locate on. They are all Key Indexes, but I just tried using the * after entering the first digit, and that worked. Buster
On Monday, 2 September 2019, 8:59:03 pm AEST, Govert Schipper <govertschipper@...> wrote: Buster, Is the field you are locating on an Alpha field? If it is Numeric, you will have to type the whole value Is the field you are locating on the first or only key segment? If not, you might try to use an * right after your value Govert Van: main@magicu-l.groups.io <main@magicu-l.groups.io> namens buster reinke via Groups.Io <buster_png@...> Verzonden: maandag 2 september 2019 12:31 Aan: main@magicu-l.groups.io <main@magicu-l.groups.io> Onderwerp: Re: [magicu-l] Locate a Record Problem Hi Keith, yes, I have Indexes on the Fields I am trying to search on. They are Alpha Fields. I have just found that if I type in the entire contents of a field eg "2622311-16", it will take me to the record, but if I just type 26 and hit locate, it takes me back to the start. It has me buggered, other Line Tables are working perfectly. Buster On Monday, 2 September 2019, 8:11:00 pm AEST, Keith Canniff <kcanniff@...> wrote: Buster,
Keith
From: main@magicu-l.groups.io <main@magicu-l.groups.io>On Behalf Of buster reinke via Groups.Io
Hello all, I am having a problem with the Locate a Record function for some Tables. Some Line Tables work with no problems. It always takes me to the first record when I enter the first digit, but for other tables, it always takes me back to the 1st record. Some of my Screen tables will Locate a Record providing I am only trying to Locate on the first field. I can't see any differences in the Line Tables that the Locate a Record work on, but I know I must have missed something. Does anyone have any idea what could be causing only some Line Tables to Locate correctly on all fields, and none of the Screen Tables to work correctly?
|
||
|
|
||
|
Re: XPA Shift+F10 hotkey and programmatic right click event
Peter Ashworth
Hi Jacek
Small follow up to this. When I fire DotNet.System.Windows.Forms.SendKeys.Send('+{F10}') within a user event fired by the button, the context menu appears, however no items on the menu are highlighted when hovering over them, and if I use the arrow keys instead of appearing in the context menu, instead the alt+space menu appears in addition top left with the menu focus seemingly grabbed by it. Manually hitting escape at this point seems to fix it. However progromatically hitting escape doesnt it exits the program. I can use a progromatic alt to fix it, it seems. Any idea why it might be stepping into alt+space mode? Manual shift f10 doesnt have the same behaviour. Thanks Peter
|
||
|
|
||
|
Re: Default VC server
Ok, it worked! And it worked as follows:
- Create an application - Import the application - Choose Add to VC-server - Choose the server (yes, now you get prompted!) - Choose the project - Go!
|
||
|
|
||
|
Re: Default VC server
The procedure I mentioned above didn't work. UP opens the application but it's not set to multi-user, i.e. no checkin/checkout option and everthing is modifiable.
|
||
|
|
||
|
Re: Default VC server
Florian,
I had to do the same thing. If I remember correctly, I exported the application, setup the application connected to the new (my) location in DevOps, then did the import.
Keith
From: main@magicu-l.groups.io <main@magicu-l.groups.io> On Behalf Of Florian Groothuis
Hi Keith,
|
||
|
|
||
|
Re: Default VC server
Hi Keith,
The problem is that the server UP wrtes the application to is a server from my former employer where I have (had) access to. I also have my own space (with the same MS-ID) where I want to put that application, but as I said, I'm not given the choice. I tried to work the other way around, move all the files to the server using VS2017 and then use the OpenFromServer-option but in all cases I got an error which had something to do with a project already existing somewhere. I will try to rename all and try again by moving the files and then open from server...
|
||
|
|
||
|
Re: Locate a Record Problem
harry@...
Hi Buster,
It's a bug in Magic. You should also fill the until value to get the correct result. Best regards, Harry Kleinsmit.
|
||
|
|
||
|
Re: Locate a Record Problem
Govert Schipper
Buster,
Is the field you are locating on an Alpha field? If it is Numeric, you will have to type the whole value
Is the field you are locating on the first or only key segment? If not, you might try to use an * right after your value
Govert
Van: main@magicu-l.groups.io <main@magicu-l.groups.io> namens buster reinke via Groups.Io <buster_png@...>
Verzonden: maandag 2 september 2019 12:31 Aan: main@magicu-l.groups.io <main@magicu-l.groups.io> Onderwerp: Re: [magicu-l] Locate a Record Problem Hi Keith, yes, I have Indexes on the Fields I am trying to search on. They are Alpha Fields. I have just found that if I type in the entire contents of a field eg "2622311-16", it will take me to the record, but if I just type 26 and hit locate, it takes
me back to the start. It has me buggered, other Line Tables are working perfectly. Buster
On Monday, 2 September 2019, 8:11:00 pm AEST, Keith Canniff <kcanniff@...> wrote:
Buster,
Keith
From: main@magicu-l.groups.io <main@magicu-l.groups.io>
On Behalf Of buster reinke via Groups.Io
Hello all, I am having a problem with the Locate a Record function for some Tables. Some Line Tables work with no problems. It always takes me to the first record when I enter the first digit, but for other tables, it always
takes me back to the 1st record. Some of my Screen tables will Locate a Record providing I am only trying to Locate on the first field. I can't see any differences in the Line Tables that the Locate a Record work on, but I know I must have missed something.
Does anyone have any idea what could be causing only some Line Tables to Locate correctly on all fields, and none of the Screen Tables to work correctly?
|
||
|
|
||
|
Re: Locate a Record Problem
buster reinke
Hi Keith, yes, I have Indexes on the Fields I am trying to search on. They are Alpha Fields. I have just found that if I type in the entire contents of a field eg "2622311-16", it will take me to the record, but if I just type 26 and hit locate, it takes me back to the start. It has me buggered, other Line Tables are working perfectly. Buster
On Monday, 2 September 2019, 8:11:00 pm AEST, Keith Canniff <kcanniff@...> wrote: Buster,
Keith
From: main@magicu-l.groups.io <main@magicu-l.groups.io> On Behalf Of buster reinke via Groups.Io
Hello all, I am having a problem with the Locate a Record function for some Tables. Some Line Tables work with no problems. It always takes me to the first record when I enter the first digit, but for other tables, it always takes me back to the 1st record. Some of my Screen tables will Locate a Record providing I am only trying to Locate on the first field. I can't see any differences in the Line Tables that the Locate a Record work on, but I know I must have missed something. Does anyone have any idea what could be causing only some Line Tables to Locate correctly on all fields, and none of the Screen Tables to work correctly?
|
||
|
|
||
|
Re: Locate a Record Problem
Buster,
Keith
From: main@magicu-l.groups.io <main@magicu-l.groups.io> On Behalf Of buster reinke via Groups.Io
Hello all, I am having a problem with the Locate a Record function for some Tables. Some Line Tables work with no problems. It always takes me to the first record when I enter the first digit, but for other tables, it always takes me back to the 1st record. Some of my Screen tables will Locate a Record providing I am only trying to Locate on the first field. I can't see any differences in the Line Tables that the Locate a Record work on, but I know I must have missed something. Does anyone have any idea what could be causing only some Line Tables to Locate correctly on all fields, and none of the Screen Tables to work correctly?
|
||
|
|
