Using the Import/Export Data Wizard, I'm trying to export a FoxPro 2.5 DOS (as dBase III) table of 15,000 records to SQL Server 2000. I keep getting this error message:
Insert Error, Column 32 ('PROG_START',DBTYPE_DBTIMESTAMP), Status 6: Data Overflow.
Invalid character value for cast specification.
I have SQL Server create the table each time I run the wizard. The new table allows NULLS in this column and I made sure to overwrite the empty date fields in the FoxPro table with blanks to make sure it would result in NULL. Originally SQL Server tried to put this as SMALL DATETIME, but when I got the message earlier, I changed it to DATETIME.
Any suggestions?hi
1) can you run a select in the fox tables, for example:
select min(col), max(col) from myTable
2) do you use any function to transform the fox date to sql date?
TIA
Abel.|||My first guess would be that you've got some data for 02/29/00, which Fox mis-interprets at 1900-02-29 (which it shouldn't accept, but it did).
If that isn't correct, the only thing I could offer would be that if you'll post the DBF (and any associated NDX, NTX, or CDX) files, I'd be willing to take a shot at converting them tonight.
-patP|||The problem is that it isn't always the same record that I'm getting the error. I'm getting this error with different tables I'm trying to convert and they all have numerous records with blank Date fields that are causing the problem.
Pat, thank you for your offer. I can try to come up with a sample data set to send to you or give you one of the smaller tables that give this error. Which would you prefer.
Showing posts with label dbase. Show all posts
Showing posts with label dbase. Show all posts
Thursday, March 29, 2012
Sunday, February 26, 2012
Error connecting through the web
Hi all, I'm new to SQL so here goes, we got a dbase we're putting up for the
web, and basically we're testing it out for connectivity, I set the system
dsn with the account that's in SQL server (got the server in mixed mode
auth), when I try to login to a page we put together I get this error
"Microsoft OLE DB Provider for ODBC Drivers error '80040e4d'
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user 'mitch'.
/ConnOpen.inc, line 10"
the username mitch exists in SQL server, the tests runs fine through
ODBC>system dsn. I looked all over the forums and can't find my issue or
anything similar, if anyone's seen this before, any pointers or ideas would
be great. ThanksA just plain "Login failed" error message indicates a bad
user name/password. If there is more with the message,
sometimes that can't help track it down. Turn on failed
login audits in SQL Server to make sure you are getting the
entire message. To turn it on, open Enterprise Manager,
right click on the server and select properties. Go to the
security tab and under Audit Level select Failed. Restart
SQL Server. The failed logins will then be logged to the SQL
Server logs.
If you are getting a full error message of login failed for
xyz. Not associated with a trusted SQL Server connection,
then it means you are trying to use a SQL login but your
server is only configured for Windows authentication. If you
need to use SQL logins, change the Authentication to SQL
Server and Windows. It's on the security tab of the
properties for SQL Server.
If you are trying to connect with Windows authentication,
then in the connection string, don't supply a user name and
password. Use Integrated Security=SSPI with an OLE DB
provider in your connection string instead of supplying a
username and password.
You may want to change drivers that you are using. The OLE
DB provider for ODBC is considered obsolete.
You can find more on connection strings at:
http://www.carlprothman.net/Default.aspx?tabid=81
-Sue
On Mon, 31 Oct 2005 14:55:06 -0800, "carlomd"
<carlomd@.discussions.microsoft.com> wrote:
>Hi all, I'm new to SQL so here goes, we got a dbase we're putting up for th
e
>web, and basically we're testing it out for connectivity, I set the system
>dsn with the account that's in SQL server (got the server in mixed mode
>auth), when I try to login to a page we put together I get this error
>"Microsoft OLE DB Provider for ODBC Drivers error '80040e4d'
>[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user 'mitch'.
>/ConnOpen.inc, line 10"
>the username mitch exists in SQL server, the tests runs fine through
>ODBC>system dsn. I looked all over the forums and can't find my issue or
>anything similar, if anyone's seen this before, any pointers or ideas would
>be great. Thanks|||Thanks for the reply, it works now, I changed the username settings in a
config file that resides in inetpub and it worked, thanks again.
"Sue Hoegemeier" wrote:
> A just plain "Login failed" error message indicates a bad
> user name/password. If there is more with the message,
> sometimes that can't help track it down. Turn on failed
> login audits in SQL Server to make sure you are getting the
> entire message. To turn it on, open Enterprise Manager,
> right click on the server and select properties. Go to the
> security tab and under Audit Level select Failed. Restart
> SQL Server. The failed logins will then be logged to the SQL
> Server logs.
> If you are getting a full error message of login failed for
> xyz. Not associated with a trusted SQL Server connection,
> then it means you are trying to use a SQL login but your
> server is only configured for Windows authentication. If you
> need to use SQL logins, change the Authentication to SQL
> Server and Windows. It's on the security tab of the
> properties for SQL Server.
> If you are trying to connect with Windows authentication,
> then in the connection string, don't supply a user name and
> password. Use Integrated Security=SSPI with an OLE DB
> provider in your connection string instead of supplying a
> username and password.
> You may want to change drivers that you are using. The OLE
> DB provider for ODBC is considered obsolete.
> You can find more on connection strings at:
> http://www.carlprothman.net/Default.aspx?tabid=81
> -Sue
> On Mon, 31 Oct 2005 14:55:06 -0800, "carlomd"
> <carlomd@.discussions.microsoft.com> wrote:
>
>
web, and basically we're testing it out for connectivity, I set the system
dsn with the account that's in SQL server (got the server in mixed mode
auth), when I try to login to a page we put together I get this error
"Microsoft OLE DB Provider for ODBC Drivers error '80040e4d'
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user 'mitch'.
/ConnOpen.inc, line 10"
the username mitch exists in SQL server, the tests runs fine through
ODBC>system dsn. I looked all over the forums and can't find my issue or
anything similar, if anyone's seen this before, any pointers or ideas would
be great. ThanksA just plain "Login failed" error message indicates a bad
user name/password. If there is more with the message,
sometimes that can't help track it down. Turn on failed
login audits in SQL Server to make sure you are getting the
entire message. To turn it on, open Enterprise Manager,
right click on the server and select properties. Go to the
security tab and under Audit Level select Failed. Restart
SQL Server. The failed logins will then be logged to the SQL
Server logs.
If you are getting a full error message of login failed for
xyz. Not associated with a trusted SQL Server connection,
then it means you are trying to use a SQL login but your
server is only configured for Windows authentication. If you
need to use SQL logins, change the Authentication to SQL
Server and Windows. It's on the security tab of the
properties for SQL Server.
If you are trying to connect with Windows authentication,
then in the connection string, don't supply a user name and
password. Use Integrated Security=SSPI with an OLE DB
provider in your connection string instead of supplying a
username and password.
You may want to change drivers that you are using. The OLE
DB provider for ODBC is considered obsolete.
You can find more on connection strings at:
http://www.carlprothman.net/Default.aspx?tabid=81
-Sue
On Mon, 31 Oct 2005 14:55:06 -0800, "carlomd"
<carlomd@.discussions.microsoft.com> wrote:
>Hi all, I'm new to SQL so here goes, we got a dbase we're putting up for th
e
>web, and basically we're testing it out for connectivity, I set the system
>dsn with the account that's in SQL server (got the server in mixed mode
>auth), when I try to login to a page we put together I get this error
>"Microsoft OLE DB Provider for ODBC Drivers error '80040e4d'
>[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user 'mitch'.
>/ConnOpen.inc, line 10"
>the username mitch exists in SQL server, the tests runs fine through
>ODBC>system dsn. I looked all over the forums and can't find my issue or
>anything similar, if anyone's seen this before, any pointers or ideas would
>be great. Thanks|||Thanks for the reply, it works now, I changed the username settings in a
config file that resides in inetpub and it worked, thanks again.
"Sue Hoegemeier" wrote:
> A just plain "Login failed" error message indicates a bad
> user name/password. If there is more with the message,
> sometimes that can't help track it down. Turn on failed
> login audits in SQL Server to make sure you are getting the
> entire message. To turn it on, open Enterprise Manager,
> right click on the server and select properties. Go to the
> security tab and under Audit Level select Failed. Restart
> SQL Server. The failed logins will then be logged to the SQL
> Server logs.
> If you are getting a full error message of login failed for
> xyz. Not associated with a trusted SQL Server connection,
> then it means you are trying to use a SQL login but your
> server is only configured for Windows authentication. If you
> need to use SQL logins, change the Authentication to SQL
> Server and Windows. It's on the security tab of the
> properties for SQL Server.
> If you are trying to connect with Windows authentication,
> then in the connection string, don't supply a user name and
> password. Use Integrated Security=SSPI with an OLE DB
> provider in your connection string instead of supplying a
> username and password.
> You may want to change drivers that you are using. The OLE
> DB provider for ODBC is considered obsolete.
> You can find more on connection strings at:
> http://www.carlprothman.net/Default.aspx?tabid=81
> -Sue
> On Mon, 31 Oct 2005 14:55:06 -0800, "carlomd"
> <carlomd@.discussions.microsoft.com> wrote:
>
>
Error connecting through the web
Hi all, I'm new to SQL so here goes, we got a dbase we're putting up for the
web, and basically we're testing it out for connectivity, I set the system
dsn with the account that's in SQL server (got the server in mixed mode
auth), when I try to login to a page we put together I get this error
"Microsoft OLE DB Provider for ODBC Drivers error '80040e4d'
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'mitch'.
/ConnOpen.inc, line 10"
the username mitch exists in SQL server, the tests runs fine through
ODBC>system dsn. I looked all over the forums and can't find my issue or
anything similar, if anyone's seen this before, any pointers or ideas would
be great. Thanks
A just plain "Login failed" error message indicates a bad
user name/password. If there is more with the message,
sometimes that can't help track it down. Turn on failed
login audits in SQL Server to make sure you are getting the
entire message. To turn it on, open Enterprise Manager,
right click on the server and select properties. Go to the
security tab and under Audit Level select Failed. Restart
SQL Server. The failed logins will then be logged to the SQL
Server logs.
If you are getting a full error message of login failed for
xyz. Not associated with a trusted SQL Server connection,
then it means you are trying to use a SQL login but your
server is only configured for Windows authentication. If you
need to use SQL logins, change the Authentication to SQL
Server and Windows. It's on the security tab of the
properties for SQL Server.
If you are trying to connect with Windows authentication,
then in the connection string, don't supply a user name and
password. Use Integrated Security=SSPI with an OLE DB
provider in your connection string instead of supplying a
username and password.
You may want to change drivers that you are using. The OLE
DB provider for ODBC is considered obsolete.
You can find more on connection strings at:
http://www.carlprothman.net/Default.aspx?tabid=81
-Sue
On Mon, 31 Oct 2005 14:55:06 -0800, "carlomd"
<carlomd@.discussions.microsoft.com> wrote:
>Hi all, I'm new to SQL so here goes, we got a dbase we're putting up for the
>web, and basically we're testing it out for connectivity, I set the system
>dsn with the account that's in SQL server (got the server in mixed mode
>auth), when I try to login to a page we put together I get this error
>"Microsoft OLE DB Provider for ODBC Drivers error '80040e4d'
>[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'mitch'.
>/ConnOpen.inc, line 10"
>the username mitch exists in SQL server, the tests runs fine through
>ODBC>system dsn. I looked all over the forums and can't find my issue or
>anything similar, if anyone's seen this before, any pointers or ideas would
>be great. Thanks
|||Thanks for the reply, it works now, I changed the username settings in a
config file that resides in inetpub and it worked, thanks again.
"Sue Hoegemeier" wrote:
> A just plain "Login failed" error message indicates a bad
> user name/password. If there is more with the message,
> sometimes that can't help track it down. Turn on failed
> login audits in SQL Server to make sure you are getting the
> entire message. To turn it on, open Enterprise Manager,
> right click on the server and select properties. Go to the
> security tab and under Audit Level select Failed. Restart
> SQL Server. The failed logins will then be logged to the SQL
> Server logs.
> If you are getting a full error message of login failed for
> xyz. Not associated with a trusted SQL Server connection,
> then it means you are trying to use a SQL login but your
> server is only configured for Windows authentication. If you
> need to use SQL logins, change the Authentication to SQL
> Server and Windows. It's on the security tab of the
> properties for SQL Server.
> If you are trying to connect with Windows authentication,
> then in the connection string, don't supply a user name and
> password. Use Integrated Security=SSPI with an OLE DB
> provider in your connection string instead of supplying a
> username and password.
> You may want to change drivers that you are using. The OLE
> DB provider for ODBC is considered obsolete.
> You can find more on connection strings at:
> http://www.carlprothman.net/Default.aspx?tabid=81
> -Sue
> On Mon, 31 Oct 2005 14:55:06 -0800, "carlomd"
> <carlomd@.discussions.microsoft.com> wrote:
>
>
web, and basically we're testing it out for connectivity, I set the system
dsn with the account that's in SQL server (got the server in mixed mode
auth), when I try to login to a page we put together I get this error
"Microsoft OLE DB Provider for ODBC Drivers error '80040e4d'
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'mitch'.
/ConnOpen.inc, line 10"
the username mitch exists in SQL server, the tests runs fine through
ODBC>system dsn. I looked all over the forums and can't find my issue or
anything similar, if anyone's seen this before, any pointers or ideas would
be great. Thanks
A just plain "Login failed" error message indicates a bad
user name/password. If there is more with the message,
sometimes that can't help track it down. Turn on failed
login audits in SQL Server to make sure you are getting the
entire message. To turn it on, open Enterprise Manager,
right click on the server and select properties. Go to the
security tab and under Audit Level select Failed. Restart
SQL Server. The failed logins will then be logged to the SQL
Server logs.
If you are getting a full error message of login failed for
xyz. Not associated with a trusted SQL Server connection,
then it means you are trying to use a SQL login but your
server is only configured for Windows authentication. If you
need to use SQL logins, change the Authentication to SQL
Server and Windows. It's on the security tab of the
properties for SQL Server.
If you are trying to connect with Windows authentication,
then in the connection string, don't supply a user name and
password. Use Integrated Security=SSPI with an OLE DB
provider in your connection string instead of supplying a
username and password.
You may want to change drivers that you are using. The OLE
DB provider for ODBC is considered obsolete.
You can find more on connection strings at:
http://www.carlprothman.net/Default.aspx?tabid=81
-Sue
On Mon, 31 Oct 2005 14:55:06 -0800, "carlomd"
<carlomd@.discussions.microsoft.com> wrote:
>Hi all, I'm new to SQL so here goes, we got a dbase we're putting up for the
>web, and basically we're testing it out for connectivity, I set the system
>dsn with the account that's in SQL server (got the server in mixed mode
>auth), when I try to login to a page we put together I get this error
>"Microsoft OLE DB Provider for ODBC Drivers error '80040e4d'
>[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'mitch'.
>/ConnOpen.inc, line 10"
>the username mitch exists in SQL server, the tests runs fine through
>ODBC>system dsn. I looked all over the forums and can't find my issue or
>anything similar, if anyone's seen this before, any pointers or ideas would
>be great. Thanks
|||Thanks for the reply, it works now, I changed the username settings in a
config file that resides in inetpub and it worked, thanks again.
"Sue Hoegemeier" wrote:
> A just plain "Login failed" error message indicates a bad
> user name/password. If there is more with the message,
> sometimes that can't help track it down. Turn on failed
> login audits in SQL Server to make sure you are getting the
> entire message. To turn it on, open Enterprise Manager,
> right click on the server and select properties. Go to the
> security tab and under Audit Level select Failed. Restart
> SQL Server. The failed logins will then be logged to the SQL
> Server logs.
> If you are getting a full error message of login failed for
> xyz. Not associated with a trusted SQL Server connection,
> then it means you are trying to use a SQL login but your
> server is only configured for Windows authentication. If you
> need to use SQL logins, change the Authentication to SQL
> Server and Windows. It's on the security tab of the
> properties for SQL Server.
> If you are trying to connect with Windows authentication,
> then in the connection string, don't supply a user name and
> password. Use Integrated Security=SSPI with an OLE DB
> provider in your connection string instead of supplying a
> username and password.
> You may want to change drivers that you are using. The OLE
> DB provider for ODBC is considered obsolete.
> You can find more on connection strings at:
> http://www.carlprothman.net/Default.aspx?tabid=81
> -Sue
> On Mon, 31 Oct 2005 14:55:06 -0800, "carlomd"
> <carlomd@.discussions.microsoft.com> wrote:
>
>
Subscribe to:
Posts (Atom)