I've had similar problems. Try to create a System DSN for the DB (start|settings|control panel|administrative tools|data sources (ODBC)) and in the same section where you select the Access DB for the DSN to point to, click the Repair button. I've had this repair my DB to the point that I could...
swampBoogie,
Thanks for the example. It worked great once I put the GROUP BY clause in there.
UPDATE t
SET StopTime =
(select dateadd(n,sum(minutes),ITIME)
from tblTest
where name = t.name
and seq <= t.seq GROUP BY ITIME),
startime = case when seq = 0 then ITIME else...
If I have the following table:
tblTest
Name ITime Seq Minutes StartTime StopTime
A 10/1/2003 8:30 AM 0 15 NULL NULL
A 10/1/2003 8:30 AM 1 20 NULL NULL
A 10/1/2003 8:30 AM 2 25 NULL NULL
A 10/1/2003 8:30 AM 3...
After reading the previous posts again, I feel like I owe SQLSister an apology for not seeing what she was trying to show me. Her advice should have been just as helpful as JamesLean's --- I just didn't read it that way. Keep up the good work. Thanks again.
LampknLn45
Well, that DELETE statement worked just fine and was much easier than a cursor. Thanks to JamesLean and SQLSister my problems have been solved.
LampknLn45
Okay, I appreciate your help in trying to provide a better way to do this but these are pretty simple SQL statements. My problem however, is not as simple. It is not possible to join my temp table to my date range table. Also, as I stated before, there may be 1 or more date ranges to filter out...
I would love to be able to do that. The problem is that there can and will be more than one date range to evaluate. So, I would need the ability to build that DELETE statement dynamically. Let me explain some more.
I have a set of records (say 1 for every day of the week) for a total of 7 in...
I have a stored procedure which uses a cursor to loop through the contents of one table and delete records from a temp table when certain date conditions exist. My procedure is now returning two result sets: The first result set is that of the cursor. The second result set (the one that I want)...
Ha, ha! Nope. Just normal lengths of 25, 10, 8, etc. Again, none of this makes much sense. I think I'm ready to just accept it and move on.
Thanks,
LampknLn45
That is probably the case. Many of my text fields from Access were converted to nvarchar fields. Still, I wouldn't expect to see such a big difference. I've converted other DB's from Access to SQL Server and not seen this.
Oh well, 55 MB isn't huge (not like I'm running out of space). Still, I'd...
(where "x" is the name of my database)
My x_Log file is around 1 MB. My x_Data file is around 55 MB. When I run "sp_helpdb x" the db_size is 55.63 MB. Again, this is a big jump from the 20 MB size in Access.
Thanks,
LampknLn45
I have looked and looked through the FAQs and forums and cannot find an answer to this.
I have an Access 2000 database that I need to convert to SQL Server 7. I create a new database in SQL Server, then use the Upsizing Wizard in Access to convert my tables, relationships, etc. (no data). I...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.