Have had no joy fixing that busted table.
We downloaded it into an Access back end and made it work for the last two weeks. The clients needs it to be back in the SQL Server because they have a whole Chemical plant that uses that data and for their reporting software.
I imported a blank table a copy of the original that was migrated back to the Access Backend.
ran a query to add all the current records and now the new table works
The problem is now I need to archive the old table and create a new one with the same name even after I changed the named to an archived style name . From an Access point of view it doesn't mater, but apparently they have a rather complicated linking arrangement and they don't want to mess with it, so the onus is on me.
Does SQL Server hold these names forever?
Any ideas?
I think I'll make a copy of the data and try deleting the table and then renaming the new one.
We downloaded it into an Access back end and made it work for the last two weeks. The clients needs it to be back in the SQL Server because they have a whole Chemical plant that uses that data and for their reporting software.
I imported a blank table a copy of the original that was migrated back to the Access Backend.
ran a query to add all the current records and now the new table works
The problem is now I need to archive the old table and create a new one with the same name even after I changed the named to an archived style name . From an Access point of view it doesn't mater, but apparently they have a rather complicated linking arrangement and they don't want to mess with it, so the onus is on me.
Does SQL Server hold these names forever?
Any ideas?
I think I'll make a copy of the data and try deleting the table and then renaming the new one.