Search results

Check with them concerning the rights. What do you have to lose? Check with them. If the IT-staff can open and create new forms with their account, this should proove it's your account at fault. Otherwise, it's another ball game.

Possible problems: 1. The DB is now in read-only (less likely). 2. Your network rights changed (more likely). You can not create stuff in this directory.

By default, a lot of form controls has a TabStop property set to True. The order in which the Tab moves is determined by the TabIndex Property. To access these properties, open the control property window. Click on other. Both properties are on the same page.

Dim strSQL as string Dim rs as DAO.Recordset Dim db as DAO.Database strSQL = "SELECT COUNT(*) as RECCOUNT FROM MILLION_TABLE" set db = CurrentDB Set rs = db.OpenRecordset(strSQL) msgbox rs.fields("RECCOUNT")

Either DCount or a "SELECT COUNT(*) FROM MILLION_TABLE" could work. I've heard DCount are as slow as hell. If there's a quicker way, I'd like to know too!

In VBA, contrary to VB, you should use .VALUE instead of .TEXT. This way, you don't have to set focus.

*Bump* Is there a way to do this? Do you need more explanations?

Not to my knowledge. What could be possible: 1. Requires Access to be installed: have a macro that imports the data. 2. Use Pc #1, which has access, and export the data on the Access file on PC #2 (requires a network of some sort). 3. Use some kind of programming software (vb, c++, java, etc.).

I want to output a query that uses parameters. How do I do that? Let's say I have 2 parameters, PDIV and PWHSE. How do I change the following line of code to use the parameter? DoCmd.OutputTo acOutputQuery, strQuery, acFormatXLS, strFile, False

Aren't you missing a clause for your IIF? Isn't it IIF(Boolean Expression, True Part, False Part)?

1. Check the number of rows in EXCEL and your imported TABLE. It may be blank due to key violation. If the number of rows are the same, go to step 2. 2. Add a step in the macro after the import: runSQL. This will delete the unwanted rows instead of you.

I've never experienced that much time difference, but then again, never used it on huge tables. Otherwise, the queries seems simple enough. Hard to optimize that!

Have you tried using a DCOUNT? I'm guessing that it's opening the recordset that takes up those nasty seconds.

Just go to TOOLS\Database Utilities\Linked Table Manager. Set your new path(s) for all the tables.

Try this in VBA (I learned it here from a previous post): DoCmd.SetWarnings False

This update FIELD2 with the first series of numbers from FIELD1: UPDATE DUMMY_TABLE SET FIELD2 = mid([FIELD1], 1, InStr([FIELD1], " ")) This remove the first series of numbers from FIELD2: UPDATE DUMMY_TABLE SET FIELD1 = mid([FIELD1], InStr([FIELD1], " ") + 1) Perform these 2, changing FIELD2...

Have you tried docmd.transferspreadsheet? I have no other lead or clue.

Have you tried to create a DAO.Database variable pointing to the other DB? Here's some code: Set dbOther = DBEngine.Workspaces(0).OpenDatabase("C:\TEST.mdb") Set myTABLE = dbOTHER.TableDefs("myTable") For Each newFIELD In myTABLE.Fields IF myTABLE.Name = "newColumn" THEN blnHasNewColumn...

I know what you mean. It bugs me too, but only a little. Perhaps you may consider: 1. Use an UPDATE query to populate the field. 2. Make a form that looks like the table datasheet (but without the auto entry). PS: Technically, it doesn't always increase by one. It tries to find the logical...

I would suggest making a relationship between these tables (if possible). I would create an outer join betweem the tables, to have all data from Table 1 and the corresponding data from Table 2. To do this, go in the query design window. Right click on the relationship.