Easiest way I have found is to export (or save) the data from Excel as a CSV file and import hte data from that file.

Try this for your udf:

CREATE FUNCTION [dbo].[ItemsRentEligible] (

    @billDate DATETIME,

    @hiDate DATETIME,

    @period INT,

    @custId INT)

RETURNS TABLE AS

RETURN(

SELECT

    OrderItem.ORDER_ID,

    OrderItem.PRODUCT_CODE,

    OrderItem.PLACEMENT_DATE,

    OrderItem.PICKUP_DATE,

    OrderItem.CUSTID,

    Products.RENT_ELIG,

    OrderItem.QTY,

    Products.TAXABLE,

    OrderItem.PRICE,

    OrderItem.BILL_DATE,

    Products.PRODUCT_DESC,

    PRODUCTS.RENT_CHG

FROM

   ...

That is possible, but I haven't ever had a request like LMtz.  This is how LMtz can grant the user access to creating views.  Unfortunately, I can't come up with...

In EM, right click on the database where the user needs to be able to create views.  Click on the Permissions tab.  There you can grant the user access the...

We had similiar issues between or Windows 2000 and Windows 2003 servers.  Can you check the configuration settings on the servers and tell us what they are?  Programs -> Administrative...

For free tools, you may want to look at SQLH2 from Microsoft.

You are welcome.

How about something like this then:

declare

@tststr varchar(128)

set

@tststr = 'Other_pg12of23_112007_Vit7_7.csv'...

The only thing I could come up with is that more than 1 row may possibly be inserted when the trigger is fired.  If you were to put the key...

try something like this:

declare

@tststr varchar(128)

set

@tststr = 'Other_pg3of7_11202006_Ndc_N.csv'

select

That is an interesting way to put it.  Can I use that analogy sometime?

Ran a few more tests using one of our production servers.  Even with adding code to insert 1000 or 5000 rows of data to the tables being created and then...

Not really a good test.  On my desktop system the numbers were a lot closer.  But what is also interesting is if you look at the execution times of each...

Actually, #tables and ##tables are more like database tables than table variables.  Yes, table variables and #tables are created in tempdb, however, SQL Server does not handle them the same...

Ninja, I agree.