Viewing 15 posts - 1,531 through 1,545 (of 2,051 total)
assuming access97
dim rs as dao.recordset
dim sqlstring as string
sqlstring="SELECT clinicianid from qryPatientCheck where ClinicianID= " & Me.ClinicianID.Value
set rs=currentdb.openrecordset (sqlstring)
if rs.recordcount>0 then
'found
else 'not found
end if
rs.close
set rs=nothing
March 10, 2006 at 6:58 am
Just a note
It assumes that FirstTreatment is always later than AssesmentDate.
Datediff is indeed more appropriate.
March 10, 2006 at 3:42 am
When you install sql server 2000 on a windows 2003 machine
ignore the warning that servicepack 3 is required.
Install sql server 2000, install servicepack 3 or higher. (otherwise 2003 only allows connections...
March 9, 2006 at 12:18 pm
what about
v=year([FirstTreatment])
w=year([AssesmentDate])
TimeOnWaitingList: ([x]-[y])+((v-w)*12)
March 9, 2006 at 12:03 pm
March 7, 2006 at 1:47 am
The same problem was in a thread only a week old. I'll see if I can find it
March 5, 2006 at 7:12 am
*can you specify with nolock for
SELECT .....
FROM master.dbo.sysprocesses WHERE hostname=host_name()
we don't want locking to occur in system tables
*for CREATE TRIGGER Via_Peticiones_TI ON dbo.Via_Peticiones
FOR INSERT
AS
specify SET NOCOUNT ON
March 2, 2006 at 2:04 pm
The Oracle installation fiddles with the registry.
Perhaps just a restart of sql server service will do.
I've allways rebooted the machines after the installation of Oracle 8 just to be sure the...
March 1, 2006 at 12:44 pm
in .NET you could make a filewatcher that reads the txt,execute
a stored proc with parameter idcard, amount,...
which checks validity & does the transaction when necessary
and returns the result to...
March 1, 2006 at 12:35 pm
Hello,
Do you have some info on the sql server version,service pack & hotfixes?
*found this whilst browsing the internet, not sure if it applies
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B827448
March 1, 2006 at 12:20 pm
Sql server is greedy on memory but releases it when other applications need it.
Usually it starts with a "low" memory usage because it hasn't stored execution plans etc in cache....
March 1, 2006 at 12:16 pm
Have you rebooted the machines?
March 1, 2006 at 11:47 am
1 day and 1 hour = 25 hours
Do you have sample data and the wished outcome?
February 28, 2006 at 12:35 pm
Because if for an odd reason the order of the parameters change (similiar with the order of columns in a table), the call will still work.
procedure myproc @startdate,@numberofdays
-> procedure myproc @numberofdays,@startdate
EXECUTE...
February 28, 2006 at 12:37 am
The user isn't system administrator or db_owner?
February 28, 2006 at 12:31 am
Viewing 15 posts - 1,531 through 1,545 (of 2,051 total)