Viewing 15 posts - 13,486 through 13,500 (of 13,838 total)
Maybe you could try reproducing the problem by running in Query Analyser - this way, you will narrow down where the problem is going wrong - obviously the SQL itself...
June 28, 2005 at 9:25 am
Try the Table Analyser Wizard in Access - haven't used it, but looks like it targets your sort of situation.
Regards
June 28, 2005 at 4:09 am
As SQL Server 2005 (not 5000) is not yet out of beta testing, there will be very few businesses using it for production purposes, whereas there are thousands using SQL...
June 28, 2005 at 2:42 am
Creating the table structure isn't hard - it's easy to get yourself a CREATE script, if you already have the table locally. Just browse to the table in the Query...
June 28, 2005 at 2:35 am
What are you trying to do exactly? It is possible to trim the time bit from a date before storing it in SQL Server, if that is your requirement.
Regards
June 28, 2005 at 2:23 am
Define 'weird result'!
I assume CompanyID is unique in Company?
Is DepartmentID unique to the Company table?
Regards
June 28, 2005 at 2:20 am
Can you send the data in the format 'yyyy-mm-dd'? This format should work regardless of American/English date worries.
Regards
June 27, 2005 at 10:20 am
If you are not going to use SQL Server in production, why use it during development? Surely you're just storing up a big headache for yourself at go-live when you...
June 27, 2005 at 10:17 am
Can't you just keep multiple versions of the database within SQL Server and take Access out of the equation? If you script all of the db changes you make, you...
June 27, 2005 at 10:06 am
The easiest way to do this is first to add the new columns to Sarah_2 - just use Enterprise Manager - making sure that the datatypes are the same as...
June 27, 2005 at 7:52 am
Not 100% sure I understand. Do you want to create a brand new column in Sarah_2 to which will be copied the Sarah_1 data?
Is there a one-to-one relationship between the two tables?
Regards
Phil
June 27, 2005 at 5:41 am
OK, this isn't so bad. If you execute a CREATE TABLE script after a DROP, it will do exactly that - delete the table and its data and then recreate the...
June 21, 2005 at 7:18 am
This sounds like an Access issue rather than a SQL Server issue - files do not "get locked for editing" in SQL Server. In Access, open the database and check Tools/Options/Advanced, ensuring...
June 21, 2005 at 5:16 am
Hi Sarah
If you are just changing the structure of an existing database, you should be able to script the required changes without losing data (but this depends on the extent...
June 21, 2005 at 5:09 am
Viewing 15 posts - 13,486 through 13,500 (of 13,838 total)