Recent content by Zeke

Wow...I thought when I ran into the first SQL having issues that I needed to address them all in the same fashion.. I have 104 other DoCmd.RunSql's that it now seems I have to test each of them to see where they get processed... I just hope it is consistant in its choice of where to process...

Thanks, I tried again with "#" and it works. I made it harder than it was.. I am new to Access so I do not know all the terminology.. I understood a pass through query to be one that executed directly against the database using the SQL provided in the RunSQL command. Seems that is incorrect...

The use of Int did not work. The Lot Recieving Date is defined in the Access table and on the form as a ShortDate, in SQL Server it is defined as a Date. When I use the Int it gives the error Operand type clash: Int inconsistent with float. researching how to make the form date a float type...

Thanks for the replies.. The SQL happens in Jet when the back end is Access and and in SQL Server when the back end is SQL Server ( the strBackend is a global variable set on startup). The DoCmd.RunSql makes it a pass through query. The code works fine for Jet. I will try the Int function to...

Ran into in issue trying to support a SS backend and an Access backend in one of my DoCmd.RunSQL's The SQL is listed below. The field tblItemReceivingHeader.OrderDate in the where clause is the is the one that appears to have issues. The date field is define in SS as "date". I have tried...

Thanks, Good to know.

2 machines - one has a2002 installed and has A2007 and the other has A2002 and A2007 runtime. Both run when the front end is A2002 regardless of backend. When A2007 (both versions) are used for the front end they get the conversion error for the string to date when run against the SQLServer...

Thanks for the reply.. I don't think the limit is the issue since Access 2007 runs fine when it is using an Access backend Db. The date conversion string was someone else's creation which seems to work (The back slashes are for recognizing the next character as a character). I must be missing...

I have an application built in Access 2002 and running in Access 2002 /2003. It is a split with an Access front end and multiple versions of the back end. Access, Sql Server 2005 Express, and Sql Serve 2008 Express. All of the versions in what ever combination run fine with the application...

Hi all... been coding to long enuff to have had a staff of keypunch operators work for me.. but I am relatively new to Access and it many iterations. hope to avoid reinventing the wheel by being here.. thanks to all who help us wondering around in the dark... laters