| re: Trouble moving Access tables to SQL back End
On 6 Sep 2005 14:55:02 -0700, "Jim M" <mandala@rci.rutgers.edu> wrote:
One tip is to use Access 2003's Upsizing Wizard (under the
Tools/Database Utilities menu). Before you run it, make sure you are
current with service packs both on the workstation and on the SQL
Server.
-Tom.
[color=blue]
>Sorry if this is repetitive, I was not able to find an answer to my
>question in this I am converting my Access tables to SQL at the request
>of a client who is having lots of corrupted data with JET - and slow
>performance. I will keep my application front end in Access (after
>several years of developing procedures, queries, forms and reports). I
>am a complete newbie to SQL server.
>
>I started by using the DTS import from SQL Server. When I try to import
>time fields (like StartTime and Duration) I get an error message.
>"Insert error... Status 6, Data Overflow.... Invalid character value
>for Cast specification."
>
>When I inititially did the import, I believe that SQL made them into
>Timestamp fields. Could that be the problem, if so, how do I keep that
>from happening?
>
>What is going on here? Thanks!
>
>Jim[/color]
| 
