You could use a stored procedure to check the existence of a table then drop it. I don't know why you want to do this from the user interface, but I would be careful about doing so. Can't you just clear the records from the existing table? Or use a temp table or make the records have a unique identifier so you can tell which one to use? Anyway, here's an example of the code to check for what you want and then create the table. You'll note thet text types are different from Access, you'll want to read up on them in Books on Line before writing your create statement.
if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[AirportRemarks]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)
drop table [dbo].[AirportRemarks]
GO
/****** Object: Table [dbo].[AirportRemarks] Script Date: 7/15/2002 1:41:20 PM ******/
CREATE TABLE [dbo].[AirportRemarks] (
[RecInd] [varchar] (3) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[AirportID] [varchar] (4) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[SiteNumber] [varchar] (11) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[RemElementName] [varchar] (8) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[RemarkText] [text] COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[RemarkID] [int] IDENTITY (1, 1) NOT NULL
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
GO
If you do this you will also want to follow this code with one or more statements granting the appropriate user rights to the table because you lose those when you drop the table.
Use something like:
GRANT SELECT ON AirportRemarks TO WebAccess
of course the actual rights you choose to grant will differ depending on what each role or user needs to have.
You would also have to add code to set up any indexes, primary key, constraints.
