The Help function has a number of topics to address problems with nulls, so you might try searching on "null values in reports" if you have a similar situation with another database you're working on.
You should have zeros on the report where the nulls were previously, and the calculations should work.
I don't anticipate problems with nulls or change properties unless there's a reason.
However, nulls steering and null depth are not taken into account, which are very important issues to be addressed.
These are increase in sidelobe levels, displacement of nulls and diminishing of null depth.
2, that due to single element failure the radiation pattern is damaged in terms of sidelobe levels, null depth and displacement of the nulls from their original position.
Using the products table below, you can see the effects that including Nulls will have on any mathematical expressions you have used:
When used for its stated purpose, null can be quite useful as shown in the Clients table in figure 1.
The nullability of a column determines if the rows in the table can contain a null value for that column.
If a row is inserted but no value is included for a column that allows null values, the database engine supplies the value NULL (unless a DEFAULT definition or object exists).
Thus, nulls that are 50 dB below the peak of the main beam are the best that can be discerned.
Using the lower order bits for nulling allows formation of nulls in the sidelobes without significant impact on the main beam (desired signal).