Search results

This is probably easy but it is giving me fits. I have some simple code that transfers an Access table to Excel. Now, I need to know how to close Excel. Obviously the code ActiveWorkbook.Close True doesn't work. I've tried defining the application, workbook and worksheet and tried .Close and...

I need help with this code. What I want to do is associate the Check.pdf file with the value "Test1" and determine if it has a certain number of pages to open one file; and if not to open a different file. I'm not even sure if I HAVE to open Test1 in order to count the number of pages...

I was able to resolve the issue by myself by replacing the subreports with subforms. :D

I have a page number field on a report; not related to the query that produces the report. I have a subreport on the report that has a PAGE field. I want the cell from the Field of the sub-report that is 1 to print on page 1 of the report and cell that is 2 to print on page 2, and so on. Is...

Was able to figure out what was causing the problem to occur. The primary table resided on a database that only I use. It was being imported to a local database. The specs were created in my database. When we created the specs in the local database, the export worked when I used the...

The datatype is set to Text. There is no property for decimals.

When I tab out of the field in the query, the "##" disappear. The CLng conversion didn't work either.

I've tried using a query; but I must be using the wrong verbage. What I have is 7 sometimes 8 numeric text characters in a field 9 characters long. What it's doing is taking 1202011 and making it 1202011.0. I've tried using Format([Field], "General Number") but that doesn't fix it because I...

Although the table I am exporting to a .txt file has all fields set up as text data types, when it pulls into the .txt file it adds a ".0" to the end of the cield. Does something in the Export specs need to change, because nothing I nothing I have changed on it seems to help. :confused:

Unfortunately, these were probably set up with support from whomever we purchased the system through. If our IT could have fixed it, I wouldn't need to find an alternate means of approaching the problem. So pretty much, I'm left with my initial question of identifying the code to pull the data...

The ODBC driver is there; but I'm not sure what the settings were before it started messing up on me to know what to change them to.

How would I go about doing that?

Until recently, I would pull all of my tables off of the AS/400 (IBM System i) through the ODBC external data interface in Access. Now when I try to pull anything over, I get the ODBC call failed error. It was suggested to me that the error was caused by a change to our SQL server...

That's exactly what I was trying to get it to do! I'm sorry it took that long to get around to the underlying question/problem. Thanks so much for your help. I can see this coming in handy more than this one time.

I can't understand why vba does not recognize the fields as null when the table is empty.

I guess what I'm really trying to get at is, does Is Null and Is Not Null work in vba?

The table is a temporary table created by a make-table query where the user inputs parameters. If the parameters do not exist in that query (say the user inputs "a" when they should input 1-10) the make-table is empty. If the table is empty, the macro progress is halted with its deletion.

Problem: How do I delete an empty table by identifying a field in the table as null. DoCmd.OpenTable "TableName" If Field Is Null Then DoCmd.Close acTable, "TableName" DoCmd.DeleteObject acTable, "TableName" Else DoCmd.Close acTable, "TableName" DoCmd.OpenForm...

Thanks very much for your help.:)

They don't know how it could have been deleted. This probably sounds pretty stupid, but what is a routine and how does one go about deleting (or restoring one, for that matter) one?