I have a table with 380 fields.

I want to experiment in marking them all global.

Is there an easy way to do this rather than going into each field and changing them individually?

Not that I'm aware of. What's the goal?

Well...

When I import, I import to a temporary table. Then I look at the data before I add it to the permanent table.

I have 10 - 15 people who can import at any one time. I was trying to find a way to:

o Keep the import table clean (and empty) and

o not have to keep up with which record any one particular user was working with... global fields are specific to a user.

So...I envisioned that each user would just see 1 record in the import table... all of their global fields.

CCB

It's an interesting concept and would work if you only import one record at a time and if you just review your own data and not everyone else's.

But no, I don't think you can change all the fields to global storage in one fell swoop.

385 fields in one table sounds like an awful lot.

How about a separate file, located locally to the user, for your temporary import point.

IdealData: That is a good point.

...I just added a Machine MAC Address field to the database and am approaching it that way.

D J: 385 is nothing. I am importing an XML data file and only have about 1/3 of the fields actually defined.

Thanks to you all.

I am importing an XML data file and only have about 1/3 of the fields actually defined.

That's no indication either way. The question is whether all 380 fields describe the same ONE thing. Perhaps they do, but there are very few objects that require tracking of 380 attributes - so DJ was right to raise his eyebrow.

Comment: I am importing 380 fields into a temporary table.... they all come from 1 xml sheet. From there I am parsing them into the correct functional tables (yes they all have to do with 1 thing but are in different tables).

I know of no other way to do this unless you are suggesting that I perform multiple imports to multiple temporary tables.

Do you think that is a better way?

Well, if they eventually go into different tables, then they do NOT describe one thing. I am afraid I cannot make any suggestions without knowing something about the nature of the data. However, keep in mind that the found set immediately after import contains only imported records - and that is user-specific.

That is a really good point. Thanks for reminding me of that.

CCB