* BUG * - Timestamp management causes error, still not fixed - Microsoft where are you?

[Atlas]

In a form, whose recordsource is set to:

SELECT dbo.

.*, dbo.[OtherTable].Display
FROM dbo.

INNER JOIN dbo.[OtherTable] ON dbo.

.ID=
dbo.[OtherTable].ID

where the field dbo.[OtherTable].Display is simply used to sort data in the
form, and it doesn't appear at all in the form, when inserting a new record
gives the error:

"Cannot insert a non-null value into a timestamp column. Use INSERT with a
column list or with a default of NULL for the timestamp column."

Looks like unnnecessary timestamp management is introduced in the underlying
query issued to the server.

The bug it has been allready properly described in a thread dated 2002:

http://groups-beta.google.com/group...ue+into+a+timestamp+column.+Use"&rnum=1&hl=en

Looks like something similar is found in the following MS Article

http://support.microsoft.com/default.aspx?scid=kb;en-us;815543

Is it possible that this bug hasn't been fixed yet?

Comments from MS appreciated.


================================================================
Windows XP + SP2
Access 2003 + SP1,
..adp project,
ADO 2.8,
MS-SQL Server 2000 + SP3a

 

[aaron.kempf]

Microsoft is a bunch of drunk fucking assholes and there are HUNDREDS
of bugs in Access that they won't fix.

POS company.

 

[Steve Jorgensen]

Nope - that's one of the many things on my list of why I don't do ADPs
anymore.