ODBC drivers not listed in SS2005 import wizard

I'm trying to import an RBASE table into SQL Server 2005. In 2000, the RBAS
E
ODBC driver was listed in the drop down list of the import wizard. It is no
t
listed in the 2005 wizard. Is there a fix for this?
Thanks,
MikeTry using the .Net Framework Data Provider for ODBC.
Then enter the DSN or the driver and connection string.
-Sue
On Fri, 26 May 2006 13:29:02 -0700, Mike
<Mike@.discussions.microsoft.com> wrote:

>I'm trying to import an RBASE table into SQL Server 2005. In 2000, the RBA
SE
>ODBC driver was listed in the drop down list of the import wizard. It is n
ot
>listed in the 2005 wizard. Is there a fix for this?
>Thanks,
> Mike|||Thanks Sue...I'll give that a try!
"Sue Hoegemeier" wrote:

> Try using the .Net Framework Data Provider for ODBC.
> Then enter the DSN or the driver and connection string.
> -Sue
> On Fri, 26 May 2006 13:29:02 -0700, Mike
> <Mike@.discussions.microsoft.com> wrote:
>
>

ODBC datasource / dataset problem

Hi,
I'm using the Visual Studio designer to create my RS reports. When I
add a new project to the solution, the new project wizard allows me to
choose ODBC as the datasource type I want to use. However, I amn't
given the ODBC option when I try to add a datasource to an existing
project. I work around this by copying and manually editing the ODBC
.rds file that was created by the new project wizard. Does anyone know
"the right way" to add an ODBC datasource to a project without using
the project wizard? I'm a bit concerned about my workaround because I
now have multiple .rds files in the same project with the same
<DataSourceID>.
Also, I don't know if this problem is caused by my workaround, but when
I use the "hacked" .rds file as a report's datasource and open the
"Data" tab I see the message:
"The query could not be loaded. Verify your connection string and query
string"
The report still runs fine, and if I open the "Generic Query Designer"
(in the "Data" tab), the query appears, and returns results if I click
the "!" button.
Thanks in advance,
DonRight click on shared data sources, add new data source. When the data link
properties box comes up it is on the connection tab, click on the Provider
tab where you can now pick ODBC.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Don" <donalmurtagh@.yahoo.co.uk> wrote in message
news:1127296726.880744.15570@.g44g2000cwa.googlegroups.com...
> Hi,
> I'm using the Visual Studio designer to create my RS reports. When I
> add a new project to the solution, the new project wizard allows me to
> choose ODBC as the datasource type I want to use. However, I amn't
> given the ODBC option when I try to add a datasource to an existing
> project. I work around this by copying and manually editing the ODBC
> .rds file that was created by the new project wizard. Does anyone know
> "the right way" to add an ODBC datasource to a project without using
> the project wizard? I'm a bit concerned about my workaround because I
> now have multiple .rds files in the same project with the same
> <DataSourceID>.
>
> Also, I don't know if this problem is caused by my workaround, but when
> I use the "hacked" .rds file as a report's datasource and open the
> "Data" tab I see the message:
> "The query could not be loaded. Verify your connection string and query
> string"
> The report still runs fine, and if I open the "Generic Query Designer"
> (in the "Data" tab), the query appears, and returns results if I click
> the "!" button.
>
> Thanks in advance,
> Don
>

Object variable or With block variable not set (was "Frank")

When trying to upsize an access database to sql server using the upsize wizard, I get the following error:
"Object variable or With block variable not set."
Any assistance is greatly appreciated.sounds like an error in the vb code. try compiling in the vba window in access and see if it kicks out any errors. i have never used the upsizing wizard and I am not sure why sql server would care about the VBA|||Upsizing wizard creates an updateable recordset using DAO (!!!) and then attempts to insert rows using rs.AddNew...rs.Update sequence within a loop over the source. The error posted means that there was a failure to create a target recordset, most likely due to datatype incompatibility (this is all most likely unless some silly things are happaning like intermittent network connectivity failures and such).|||Thanks all for most helpful comments. Not too sure how to correct this in order to get a target recordset in that this is my first time doing this.

Any further comments welcomed.

Thanks once again for your time and effort in assistingme.