Access 2007 + SQL Server 2005 + Vista x64

Hello,

I am looking for a solution to the problem named Table was skipped, or export failed. Here's the story:

I have a desktop with Vista Ultimate x64 and Office 2007. I want to export a database from Access MDB (about 2Gb, 110 tables) to SQL Server Express Express (Advanced). The simple solution > upsize wizard.

- create new database

- server name, used trusted connection, some database name
- I select all tables
- I unselect table's attributes

- create new Access server/client application

and every time I have Table was skipped, or export failed. The same thing happens when I create new MDB with one table (some random values)!

The strange thing that on laptop with XP + SQL Sever 2005 Express (Simple) and Access XP upsizing the same database works fine!'

one other issues of a rookie:

I wanted to access a database (randomly created) on Vista with the Access on my laptop. Both PCs are in the same network I can ping both, but when I try to connect to IP_desktop\SQLEXPRESS Access posts connection error. Why?

P.S.

When installing SQL Server on Vista I have only a problem with IIS and ASP.NET, but it shouldn't be a problem.

For the first issue, plase post the complete error message, for the second quesstion, you should enable the SQL Server Browser service and make sure that remote connections are enabled to the SQL Server machines (for more information see the screencast on my site)

Jens K. Suessmeyer

http://www.sqlserver2005.de

about supersocket failed

Hi!
When i install a layered SPI, the SQL will report supersocket failed while
bind to port 1433 ? when i uninstall the layered SPI, it is OK. but i
disable the SPI by move the SPI down, it also report failed? who can tell me
the reason and how to avoid it?
Thanks!
Xiaorun huangHi
Have you run netstat -b to see what is using the port?
John
"xiaorun" wrote:

> Hi!
> When i install a layered SPI, the SQL will report supersocket failed while
> bind to port 1433 ? when i uninstall the layered SPI, it is OK. but i
> disable the SPI by move the SPI down, it also report failed? who can tell
me
> the reason and how to avoid it?
> Thanks!
> Xiaorun huang
>
>|||I had see and it is sqlservr use the 1433 port, and i can connect to 1433
port and use SQL server, but it has this error in the event log.
Thanks!
Xiaorun huang
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:CE72090D-0F89-4FFF-B98E-6E7620DE129A@.microsoft.com...
> Hi
> Have you run netstat -b to see what is using the port?
> John
> "xiaorun" wrote:
>|||Hi
You can get the error message whe n the account that the SQL Server service
is running as, does not have local admin rights, but how that would be linke
d
to loading SPI and why you would not get it without, I am not sure.
John
"xiaorun" wrote:

> I had see and it is sqlservr use the 1433 port, and i can connect to 1433
> port and use SQL server, but it has this error in the event log.
> Thanks!
> Xiaorun huang
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:CE72090D-0F89-4FFF-B98E-6E7620DE129A@.microsoft.com...
>
>