i'd use

set nocount on

Declare @strSQL as varchar(100)

Declare @Out as Integer

set @strSQL='Set @out=(select Count(*) from ' + @Table+')'

exec sp_executesql @strsql

select @out

it's just the next revision number (like 3.1)

you can find sql server service pack 3a on http://www.micorosft.com/sql

service pack 3 and service pack 3a both report the version of

8.00.760

although 3a includes the SQL slammer protection. Both of...

have a look at

http://www.microsoft.com/sql/reporting/productinfo/RS_AuthoringDemo.asp

you will see how it's done

but yes, a new project type is available - SQL report

are you planning to write all of the reports yourself? that's...

100Mbps - no worries - i've been used to deploying these acess/SQL solutions across a 512kbps ADSL line(where it's difficult to get a higher speed line installed - such as...

there is a web cast that you can view at http://www.microsoft.com/sql/reporting

this shows how easy it is to create and distribute reports, although it's a bit cheesy for my liking.

crystal...

there are some network throttling (and monitoring) tools that you can download (we used them to simulate moving from citrix published apps to a Client/server app over the WAN.

i'm not...

not quite that way,

access calls gets the results steadily using as much network bandwidth as it can.

the reult set is available immediatley, (which is why you can navigate quickly...

if this is a one way process (from pub to sub) then have you considered using log shipping ?

according to microsoft docs you can't.

what you could do though is back up your user databases and uninstall sql server - then install sql standard and restore your databases.

proboably best...

just out interest, if you switched to simple mode, why did you back up the log ??

just run a checkpoint command????????

sql server and access will drip feed the results through the connection.

what you can do to give your users the perception of a faster connection is use the FAST...

you could write out the stored procedures to text files and then use ISQLW.exe to run them.

that way you can use xp_cmdshell to call ISQLW

declare @strsql nvarchar(4000)

if (select system_user)='mike'

begin

print 'True'

set @strsql='create procedure usp_test as select NULL'

exec sp_executesql @strsql

end

else

begin

print 'False'

set @strsql='create procedure usp_test as select NULL'

exec sp_executesql @strsql

end

you can import data from foxpro fairly easily.

right click on your new database and select all tasks, then choose import data.

as your source choose the driver for Visual...