PROBLEM SOLVED....
To all that have tried to help me, I want to say thank you to all of you. Turns out that I made a silly mistake in my config.g. dc42 posted , you should put the M92 command before and the firmware will take care of the M350 when it sees it based on your M92 settings. If this can help someone else from making this mistake or helps some one figure out whats wrong, then the past month of frustration will be worth it. Thanks again for the support...and the patience for a noob.

I made a choice between one of two boards for my printer. I most definitely choose the right one.
thanks,
RJ

@phaedrux , @joergs5
I just tried this in my config.g
M92 X80 Y80 Z80 E420 ; Set steps per mm x80 y80 z175 z80 z85
M350 x64 y64 Z128 ; Configure microstepping with interpolation
;M92 Y320 Y320 Z1400 E420 ;mod to test 64 micro stepping This resulted in the normal movement.
changed to this:
;M92 X80 Y80 Z80 E420 ; Set steps per mm x80 y80 z175 z80 z85
M350 x64 y64 Z128 ; Configure microstepping with interpolation
M92 Y320 Y320 Z1400 E420 ;mod to test this resulted in movement on the Y while doing a G1 x100
So the answer is , Yes I can duplicate it.
Other than my reply earlier, I have no clue why this is happening. I just know that I can move forward now..
RJ

Here is what I did. I have a mushroom button type of E Stop button, that is a single normally closed switch. I have a relay that is controlled by the Atx on /off in DWC.
I used e1stop pin to act as a trigger. I do not use the M112 command., I use the M999 command.
Here is the entry in the config.g file
M81 C"pson" ; allocate the PS_ON pin to power control but leave power off
M950 J1 C"^e1stop" ; Assign Pin1 to e1stop the terminals on the E stop switch is wired to the GND and E1 stop pin on the Duet board
M581 P1 T10 S1 R0 ; Enable Emergency Stop
M582 T10 ; when triggered run trigger10.g

Here is the contents of the trigger file.;testing the trigger system
M81 ; SHUT THE POWER OFF
M291 P"E STOP ACTIVATED" S1 T5 ;Lets me know something happened
G4 S2 ;This give the power supply time to drop and stops the error messages as the VIN drops
M999 ; reboots the duet board
;END
It stays in a loop until the E stop switch is reset. Hope this helps.

@t3p3tony
Thanks for the kind words, but I have just started the learning curve.

@deckingman Thanks, sometimes to close to the forest to see the trees!

@joergs5
Yes.. I can't begin to tell you how many times that I looked at it and missed it.. And I wear glasses!

@dc42 Amen to that!!!!

@dc42 @ everyone
Thank You Dave!!! You made me find the problem. By going in fresh this am and starting to do the test, I discovered that in my original config.g file posted here, the original M92 statement was incorrect, it read "M92 Y320 Y320 Z1400 E420 ". I guess my mind corrected it every time I looked at it. Your #4 test was what made me catch it. So I have corrected it and all seems to be correct. I ran the test with the bad M92 statement and got this
9:43:05 AM
M92
Steps/mm: X: 349.956, Y: 320.000, Z: 1400.000, E: 420.000:420.000:420.000:420.000:420.000:420.000:420.000:420.000:420.000

I can't really comment on the inner workings, but it shows me that the two motors were not in sync. So my problem is solved and the mystery of why is now as well.
I apologize for all of the time and effort that was put in to finding my stupid mistake and thank everyone for their time and effort.

@joergs5

I was going to try it with the end stop on either end the of the Z. So I had done that before my issue was discovered. I haven't gotten to those tweaks or others, like the accelerations, jerk factor and lots of others. Still learning about a lot of this. I do appreciate the input.
RJ

@dc42
Yes I can. I posted that result here : https://forum.duet3d.com/post/55484
I had found a post that you had done about putting the M92 Xxx Yxx, with the steps set for 1/16 step rate before the M350 command. I changed that and my issue with the Y moving with the X and vice versa, Stopped. I was asked if I could replicate it. I tried and I could. I thought maybe I had something else that could effect it in my config file, so I posted it after I had changed it, leaving the original statements marked in it, obviously commented out.

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet Ethernet 1.02 or later
Firmware Version: 1.21 (2018-03-21)
Web Interface Version: 1.21Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet Ethernet 1.02 or later
Firmware Version: 1.21 (2018-03-21)
Web Interface Version: 1.21
RJ

@deckingman
So your tried this and couldn't replicate the movement? Here is my modded config file, with some notes. Maybe I have messed something else up as well..and just waiting to bite me.
; General preferences
M111 S0 ;DEBUGGING OFF
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like MARLIN
M667 S1 ; Select CoreXY mode

; Network
M550 PRJPRINT ; Set machine name
;M552 S1 ; Enable network
M552 S1 P192.168.1.99 ;SET IP ADDRESS
M553 P255.255.255.0 ;SET SUBNET MASK
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

; Axis Limits
M208 X325 Y415 Z0 S0 ; Set axis maxima
M208 X0 Y0 Z-600 S1 ; Set axis minima

; Drives M569: Set motor driver direction, enable polarity and step pulse timing Parameters
;M584 X1 Y0 ; test for Ian Swapping the A & B connectors test
M569 P0 S1 ; Drive 0 goes FORWARDS Rnnn Driver enable polarity: 0 = active low, 1 = active high (default 0)
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S0 ; Drive 2 goes forwards
; If I put the M350 command here and comment out the existing M350 (2 lines down)
M92 X80 Y80 Z80 E420 ; Set steps per mm @ 1/16 step rate
M350 x128 y128 Z128 ; Configure microstepping with interpolation
;M92 Y320 Y320 Z1400 E420 ;mod to test 64 micro stepping <----this one will cause the movement on Y while moving x
;M92 X320 Y319 z1400 E420 ; to test to see if it corrects the speed <----This one stops the Y movement while moving x
M566 X600 Y600 Z100 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z4000 E1200 ; Set maximum speeds (mm/min) CHANGED FROM 6000 TO 600 Z NO CHG
M201 X500 Y500 Z250 E250 ; Set accelerations (mm/s^2)
M906 X1500 Y1500 Z1500 E800 I40 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Endstops
M574 Z1 S0 ; Set active low endstops
M574 X1 Y1 Z2 S0
;M574 X1 Y1 S3 ; Set endstops controlled by motor load detection

; Z-Probe
;M558 P0 H5 F120 T6000 ; Set Z probe type to switch and the dive height + speeds
;G31 P600 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height

;M557 X15:327.9 Y15:391 S20 ; Define mesh grid

; Heaters
M140 H1 ; Remap heated bed to heater 1
M301 H1 P-1 ; Set heater 1 to bang-bang mode
M305 P0 X200 ; Configure thermocouple for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 X201 ; Configure thermocouple for heater 1
M143 H1 S280 ; Set temperature limit for heater 1 to 280C

; Fans
M106 P0 S1 I0 F500 H1 T45 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

; Tools
M563 P0 D0 H0 ; Define tool 0
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C

; Automatic power saving
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss

; Custom settings are not configured

@joergs5 I am not sure what you are asking me.
the first example puts the step rate at 1/16 M92 X80 Y80 followed by the M350 changing the step rate to 1/64 (letting the firmware adjust the steps per mm). This works correctly.
The second example puts the step rate at 1/64 (M350 X64 Y64) followed by the M92 command, which gives the same thing, but spells out the steps per mm. This does not work correctly. Maybe doing it this way causes the firmware to miss a variable or miscalculate the steps due to the order it gets the settings. I am thinking of posting this question to dc42. He might have some knowledge why this happens.
rj