Recent content by drkhelmt

I would just change the security permissions in windows for that directory to restrict the users to read-only access. I have a Purchase Order database that I need read and write access, but want everybody else to be able to read but not write to and that is now I accomplish this. If you need...

Why can't you delete the lock file? Please continue with that error. If you can't delete it because the lock file is in use, disable the network card (to forcefully kick users off the computer) then delete the file. Hope this gets you closer to the solution. Andrew a.k.a. Dark Helmet...

I had this same problem with one of my databases. What I found to be the problem (through shear luck) was that my computer's network card was dieing, causing lost packets which in turn crashed the database. I don't know where, but I got an ldb viewer which gave me no information since it...

Nevermind.... my mistake. I changed the querynames but did not change the data in the countrol sources. I still don't get anything in the field list, but I guess that probably has to do with the crosstabs being dynamic in columns. Thank you for the answers! Andrew a.k.a. Dark Helmet "What's...

Thanks for the response. It worked.... kinda. Now I don't get any fields in the field list for the reports. I can run the queryies just fine and get the data needed, however, when I run the report, I get: "The Microsoft Jet database engine does not recognize '' as a valid field name or...

This should be a simple deal but I can't seem to figure it out. Any help is appreciated. I have 2 queries- productionWork: SELECT production.productionDate, employee.name, clProduction.hours FROM production INNER JOIN (clProduction INNER JOIN employee ON clProduction.employeeID =...

My first thought would be to turn that "server" into a linux box. Its free and can do enterprise level stuff. I think, but not sure, that your 10 user limit is a function of Windows and not Access. As for upgrading to MySQL, with only 25 users, I don't think that is necessary. Also if...

Have you looked at parse? Hope this gets you closer to the solution. Andrew a.k.a. Dark Helmet "What's the matter Colonel Sandurz? Chicken?

Riiight... thats what I was thinking but not what my code was exactly doing... try this: dim rst as dao.recordset dim dbs as dao.database dim i as integer dim n as long dim sqlst as string set dbs = currentdb set rst = dbs.openrecordset(table1) i = 1 n = 1000001 do while not rst.eof sqlst...

Yeah, that's too many to do manually. OK, then lets change the above code a little... dim rst as dao.recordset dim dbs as dao.database dim i as integer dim n as long dim sqlst as string set dbs = currentdb set rst = dbs.openrecordset(table1) i = 1 n = 10001 do while not rst.eof i = i + 1...

If you don't need two tables it may just be easier to add a field to table1. How many records we dealing with? If there's not too many, you may just consier doiing and update query and say if field on is between x and y, update field2 to xy. Hope this gets you closer to the solution...

Yes, because for every order (orders table) you have multiple order itens (orderItems table). The location is a function of the order (assuming all items get shipped to the same location). When you design your forms, you have a Order form that is tied to your order table. Then you have a...

Oh, well, in that case... dim rst as dao.recordset dim dbs as dao.database dim i as integer dim n as long dim sqlst as string set dbs = currentdb set rst = dbs.openrecordset(table1) i = 1 n = 1 do while not rst.eof i = i + 1 if i = 35 then 'we're on the 35th record mx = mx + 1...

How often does table1 incriment by 35? If it is less than once a day, you might consider puting some code in the onOpen event of a form to compare table2 to table1 and if necessary incriment it. Another way would be to add basically the same code to the code/form that is making table1...

I'm a little unclear as to the orders and ordersID tables. Is the OrdersID table supposed to be like an orderItem table? If so, you should probably have an OrderItem: orderItemID, orderID, ... Order: orderID, ... I think lynchg is on the right track with a location table. You may also...