Control can't be edited; it's bound to a replication system column 'TableName'.
Stewart Berman
names TableName and FieldName and a bunch of others. This table has had a
small number of records added to it (37) over the life of the database.
Suddenly, the two fields TableName and FieldName cannot be edited. That is
even if the table is open as a table and you try to type a new record. When
you do that an error message is briefly displayed in the left hand end of
the Access main window's status bar. For example if you try to input
anything into the TableName field you will be blocked and you will briefly
see:
Control can't be edited; it's bound to a replication system column
'TableName'.
How do I unbind it? Access 2007 does even support replication in an accdb
file.
David W. Fenton
news:0264t5hiq7epnte4q...@4ax.com:
That's pretty weird!
Is the field editable when just open the table datasheet?
If so, there's either something in the recordsource of your form
that makes that field uneditable, or you've set the controls or the
form to be uneditable.
Have you tried creating a new form to display the same data (or just
the problem fields)? If that works, it might provide a clue as to
what the real problem is. Or, if it doesn't work, it would at least
show it's not something specific to your original form.
Also, keep in mind that if your ACCDB front end links to a
replicated front end, the replication error message could be correct
(though you don't say your app is split -- it should be, of course,
as should all Access apps, in fact).
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Stewart Berman
I think you missed:
>> FieldName cannot be edited. That is even if the table is open as
>> a table and you try to type a new record. When you do that an
IOW, I have the same problem if I just open the table in datasheet mode.
The application is split but the back end is an accde file type and
therefore does not support replication.
Where in the Access system tables are the replication settings stored?
David W. Fenton
> I think you missed:
>>> FieldName cannot be edited. That is even if the table is open
>>> as a table and you try to type a new record. When you do that
>>> an
> IOW, I have the same problem if I just open the table in datasheet
> mode.
You're right, I missed that you were talking about a fieldname in
table design view.
> The application is split but the back end is an accde file type
> and therefore does not support replication.
Is it possible the file was an unreplicated MDB converted to ACCDB?
It is not possible to delete replication fields from a table after
it's been unreplicated, except using certain utilities.
I would suggest recreating the table structure under a new name,
appending the data and then deleting the old table.
> Where in the Access system tables are the replication settings
> stored?
There are a dozen or so replication tables:
MSysConflicts
MSysExchangeLog
MSysGenHistory
MSysOthersHistory
MsysRepInfo
MSysReplicas
MSysRepLock
MSysSchChange
MSysSchedule
MSysSideTables
MSysTableGuids
MsysTombstone
MSysTranspAddress
There is no editable information in any of these tables.
Stewart Berman
None of the tables you listed exist in the database.
It is my understanding that the database was originally created in Access
2007. The table that developed the problem was created fairly recently --
actually within the last couple of weeks.
However, I think I found the cause of the problem. The table was created
using a make table query that joined the MSysComplexColumns and MSysObjects
table to produce a table containing the table name - field name pair for all
attachment fields in the database. The ColumnName field in the
MSysComplexColumns provided the field name and the Name field in the
MSysObjects table provided the table name. Although both fields are defined
as text fields in their respective tables they appear to have some
additional attributes that look like replication even though it is not.
Creating the target table first and then runing the query as an append query
seems to have solved the problem.