Upsizing Access 2003 db with SourceSafe 6.0d to SQL Server 2005 - Crashes
I have happily been using Access 2003 sp1 with SourceSafe 6.0d (build
31222) for two years. However, application database is being upsized
to SQL Server 2005, currently sp2 Developer Edition. I can use Source
Safe from the SQL Server database though there were warnings about
encoding. However, Access crashes with 'Microsoft Office Access has
encountered a problem and needs to close' if I try to relink my
checked out tables to SQL Server while Access is linked to Source Safe
using an upsizing utility. If I remove the database from Source Safe
I can relink the tables to SQL Server fine. However, if I try to add
the relinked database to a new Source Safe project Access again
crashes. I get none of the usual prompts about the new Source Safe
project nor adding all objects to Source Safe. The file name given
in the database properties does match the actual file name. OS is XP
Pro sp2. I can relink the Northwind database and add it to Source
Safe. A couple of my tables have spaces in their tables names but
otherwise all are standard alphanumerics. Any ideas? Many Thanks.
.
Relevant Pages
- Re: return multiple rows from sql statement
... Concatening SQL ... strings from input values is almost certainly a safe path to SQL ... All characters that are entered in the fields make their way into the database unaltered. ... The insert of what surprisinlgly was NOT a syntax error, but a string called "mysql_insert_id" into an integer field resulted in the value zero being put in. ...
(comp.lang.php) - Re: return multiple rows from sql statement
... strings from input values is almost certainly a safe path to SQL ... Also, being a MySQL function, it knows what MySQL needs or uses. ... All characters that are entered in the fields make their way into the database unaltered. ... The insert of what surprisinlgly was NOT a syntax error, but a string called "mysql_insert_id" into an integer field resulted in the value zero being put in. ...
(comp.lang.php) - Re: return multiple rows from sql statement
... strings from input values is almost certainly a safe path to SQL ... Also, being a MySQL function, it knows what MySQL needs or uses. ... The insert of what surprisinlgly was NOT a syntax error, but a string called "mysql_insert_id" into an integer field resulted in the value zero being put in. ... derived form..now normally I update the database, then read the data from the database back into the form: In this case I was testing 'failed to update, re-enter some data' and the backslashed stuff gave me issues with quotes and backslashes. ...
(comp.lang.php) - Re: return multiple rows from sql statement
... strings from input values is almost certainly a safe path to SQL ... All characters that are entered in the fields make their way into the database unaltered. ... Also, mysql_real_escape_stringwill take care of NOT altering data when inserting it, providing you don;t have any hidious mechanisms like magic quotes enabled. ... The insert of what surprisinlgly was NOT a syntax error, but a string called "mysql_insert_id" into an integer field resulted in the value zero being put in. ...
(comp.lang.php) - Re: Database change management process
... your other environments via a controlled process (i.e. DBA applies database ... (something like source safe that controls the code changes for our ... processes of change control for sql server databases and so on... ...
(microsoft.public.sqlserver) |
|
