Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Calc doesn't support the "entire column addressing" at present.

There is an old feature request filed as bug FDO#48571 on 2012-04-11. There wasn't much support for it, obviously, despite the fact that the topic comes back now and then in the forums.

(The odf documents specify a 'RangeAddress' alternative to that effect for the persistent (file) representation. It may get implemented one day. The feature request, however, is not yet assigned to a developer. You may try to vote it up.)

Calc doesn't support the "entire column addressing" at (or "entire row")at present.

There is an old feature request filed as bug FDO#48571 on 2012-04-11. There wasn't much support for it, obviously, despite the fact that the topic comes back now and then in the forums.

(The odf documents specify a 'RangeAddress' alternative to that effect for the persistent (file) representation. It may get implemented one day. The feature request, however, is not yet assigned to a developer. You may try to vote it up.)

Calc doesn't support the "entire column addressing" (or "entire row")at row") at present.

There is an old feature request filed as bug FDO#48571 on 2012-04-11. There wasn't much support for it, obviously, despite the fact that the topic comes back now and then in the forums.

(The odf documents specify a 'RangeAddress' alternative to that effect for the persistent (file) representation. It may get implemented one day. The feature request, however, is not yet assigned to a developer. You may try to vote it up.)

Calc doesn't support the "entire column addressing" (or "entire row") at present.

There is an old feature request filed as bug FDO#48571 on 2012-04-11. There wasn't much support for it, obviously, despite the fact that the topic comes back now and then in the forums.

(The odf documents specify a 'RangeAddress' alternative to that effect for the persistent (file) [file] representation. It may get implemented one day. The feature request, however, is not yet assigned to a developer. You may try to vote it up.)

Calc doesn't support the "entire column addressing" (or "entire row") at present. Yo will have to explicitly include the row numbers like in "A1:A1048576". The hard coded number of rows (2^20) will surely not get increased soon. The disadvantages concerning deleted rows can only be avoided, I think, using OFFSET().

See also: ask44177WholeColumnTest001.ods

There is an old feature request filed as bug FDO#48571 on 2012-04-11. There wasn't much support for it, obviously, despite the fact that the topic comes back now and then in the forums.

(The odf documents specify a 'RangeAddress' alternative to that effect for the persistent [file] representation. It may get implemented one day. The feature request, however, is not yet assigned to a developer. You may try to vote it up.)

EDITING = Waiting is over! V5.0.0 is released! = References like A:A, 1:5, C:F, 7:7 allowed now! = EDITING

Calc doesn't support the "entire column addressing" (or "entire row") at present. Yo will have to explicitly include the row numbers like in "A1:A1048576". The hard coded number of rows (2^20) will surely not get increased soon. The disadvantages concerning deleted rows can only be avoided, I think, using OFFSET().

See also: ask44177WholeColumnTest001.ods

There is an old feature request filed as bug FDO#48571 on 2012-04-11. There wasn't much support for it, obviously, despite the fact that the topic comes back now and then in the forums.

(The odf documents specify a 'RangeAddress' alternative to that effect for the persistent [file] representation. It may get implemented one day. The feature request, however, is not yet assigned to a developer. You may try to vote it up.)