Search results

I have done some testing...it appears all of our 2003 servers have the same problem with access 97. One server gave this error: The instruction at "0x00194b78" referenced memory at "0x00194b78". The memory could not be "written". Clik ok to terminate the program. Click cancel to debug the...

The error provided on the original post is what comes from the event viewer. I see no broken references (at least none are labeled as missing.) I gave the root drive (c) access to everyone and full control. I have reinstalled access, and I have even reinstalled the terminal services server...

It also happens on creating a new button on a form for a blank database...it closed automatically.

A brand new 2003 and access 97 server does not work either...I still get the same problem. I am still searching on the web for more solutions.

I have recently done a fresh install of access 97 to our 2003 server. I load up an access app, it brings up a form with a button...I clidk the button, and it closes the app with no errors, and leaves the ldb file in tact. Checking the event viewer, I get this message: Faulting application...

nm, found it...DoCmd.SetWarnings false...thanks for all of your help!

Ok, i have everything working now...yay! here isthe code that works: Dim strSplHandling As String Dim strCustNum As String Dim intOrderNum As Double Dim strSplHandlingCustMaster As String Dim rs As DAO.Recordset Set rs = CurrentDb.OpenRecordset("SELECT ORDERS.SPL_HNDL AS SplHandling...

I removed square brackets so it looks like this: Set rs = CurrentDb.OpenRecordset("SELECT ORDERS.SPL_HNDL AS SplHandling, ORDERS.[ORDER #] AS OrderNum, ORDERS.[CUSTOMER #] AS CustNum FROM ORDERS WHERE (((ORDERS.[ORDER #]) = 418626))") and I get the follwing error: so I changed my query to...

I thought that also, and it didn't work. So, i replaced the form part with just an order number to see if it works, and it doesn't...here is what I havce that doen't work also: Set rs = CurrentDb.OpenRecordset("[SELECT ORDERS.SPL_HNDL AS SplHandling, ORDERS.[ORDER #] AS OrderNum...

Does it matter that the Orders table is a sql linked table?

yes...it is spelled correctly. I created the query in access and simply copied / pasted the sql code into the vba code.

Set rs = CurrentDb.OpenRecordset("[SELECT ORDERS.SPL_HNDL AS SplHandling, ORDERS.[ORDER #] AS OrderNum, ORDERS.[CUSTOMER #] AS CustNum FROM ORDERS WHERE (((ORDERS.[ORDER #])=[Forms]![ORDERS INPUT FORM]![ORDER #]))]") I get an error on that line saying can't find the input query or table...is it...

here is what I currently have Dim strSplHandling As String Dim strCustNum As String Dim intOrderNum As Integer Dim strSplHandlingCustMaster As String Dim rs As DAO.Recordset Set rs = CurrentDb.OpenRecordset("[SELECT ORDERS.SPL_HNDL AS SplHandling, ORDERS.[ORDER #] AS OrderNum...

I have a subform inside of a form. For that subform, on its focus, I wish to run some code. I want the code to run a query: SELECT ORDERS.SPL_HNDL AS SplHandling, ORDERS.[ORDER #] AS OrderNum, ORDERS.[CUSTOMER #] AS CustNum FROM ORDERS WHERE (((ORDERS.[ORDER #])=[Forms]![ORDERS INPUT...

any ideas?

We are using access 97 and I have a linked table to sql 2000. A couple of weeks ago, our sql server crashed and we had to completely rebuild it / restore all of the data. Ever since then, only one of our linked sql tables in access is acting up. Whenever we go to edit a line (sometimes, not...

for sure :)

Actually, since we had numerous other problems, we have reverted back to access 97...so, until we decide to upgrade again (maybe in another 10 years :P), this issue is dead. We have numerous databses created in 97 that are just too old to upgrade to 2007, the databases close all the ime with...

access created the macro.

I am using the import method in a macro...whatever access does.