Will NOT using #property strict cause an EA to not send trades?

I have two of the same EAs running live on 2 different real accounts. One on a vps and one local.

The vps version was loaded without #property strict and the local one did.

The reason is that the code is not 100% perfect and I did not want the EA running or not running unexpectedly without being able to be right in front of it. I understand that the #property strict command will cause an ea to stop running if it doesn't like something like bad arrays and I can't afford to have the ea stop running without me knowing it since it runs without putting SL TPs on the broker's server in public view. It does have stops and tp exits but they are completely hidden and I don't want to put fake sl tp levels with the broker either.

In any case, at the start of the new 4hr bar, the local copy with property strict executed perfectly as intended but the vps copy w/o property strict just sat there, with no movement, no messages, no errors, nothing, like it wasn't even loaded but it was.

Come to think of it, yesterday the non property strict version fired off an unexpected trade that didn't show up locally either.

Can not using property strict alter the trade execution of an ea?

Yes,it is possible if not coded correctly.

My opinion, you should always use #property strict. Not using it means that you get away with poorly written code and your will have unexpected behavior in your EA. My advice would be to make sure to always check for the size of an array using the ArraySize() or iBars() function always make sure you use a valid index reference. There is a good reason why the out of range error occurs, meaning you are trying to read data where none exists and suppressing the error will only lead to trouble.

I agree. I'm working on getting the array issue straightened out. Biggest issues (read: weaknesses) coding MT4 personally have been coding for arrays and loops, which is also hindering testing and implementing more robust methods. For now, I'm going to load the strict version on the vps and see how it goes un-monitored. I'm also thinking that it could be a variable pre initialized to zero, when in actual market conditions it's really a one, and the ea is now waiting for the next signal instead of firing off the first signal that wasn't triggered b/c of the pre initialized zero. I may work on some way to read the data and previous signals first but for the time being I think I may use GVs and then initialize the variable manually. There are just so many microscopic things that could be off here, but the first step is to uncomment property strict on the vps and see how it goes.