Editing Link Specifications and system tables

  • Thread starter Thread starter Rod
  • Start date Start date
R

Rod

I want to create lots of Link Specifications, preferably on the fly.

These are stored in the tables MSysIMEXColumns and MSysIMEXSpecs, but a user
is preventing from appending or editing them.
Is there a way around this, is it sensible or is there a better way?

thanks in advance

Rod
 
Rod said:
I want to create lots of Link Specifications, preferably on the fly.

These are stored in the tables MSysIMEXColumns and MSysIMEXSpecs, but a
user is preventing from appending or editing them.
Is there a way around this, is it sensible or is there a better way?

thanks in advance

Rod
Click to expand...

To answer my own question for the benefit of those on the same journey.

You can add, edit and delete records in these tables using queries.
 
Rod

I was under the impression that the system tables were off-limits. How are
you using queries to modify these tables?

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.
 
Jeff Boyce said:
Rod

I was under the impression that the system tables were off-limits. How
are you using queries to modify these tables?

Regards

Jeff Boyce
Microsoft Access MVP
Click to expand...


Just treat it as a normal table and write a query. I happen to have this
database set for exclusive use but I don't know if that is important.

You don't happen to know what the width field is for. I am importing CSV
files so you would expext it is not important.
However if you change them things go wrong. For the most part the width is
Len(Fieldname)+1, but sometimes it is bigger by anything from 2 to 6.


regards
Rod
 
Rod said:
Just treat it as a normal table and write a query. I happen to have this
database set for exclusive use but I don't know if that is important.

You don't happen to know what the width field is for. I am importing CSV
files so you would expext it is not important.
However if you change them things go wrong. For the most part the width is
Len(Fieldname)+1, but sometimes it is bigger by anything from 2 to 6.


regards
Rod
Click to expand...
Answering my own question again, it is the maximum length + 1 of the data in
the column in the first 25 rows including the title row.
 
the column in the first 25 rows including the title row.


That is set in the registry.


Note that these table have not remained entirely stable
over the last 15 years, and may change again.

Personally, I write all my import stuff in VBA, (OK,
I wrote it 15 years ago), and import to a text table,
and then from the text table to the destination table.

Because the easy import stuff doesn't handle variations
in the import format very well, like when you have a
missing field, or a magic field, or a field too long, or whatever.

And because the import specs are located in CurrentDB,
and I do a lot of importing from CodeDB.

(david)
 
Back
Top