Search results

Hello Dave ... While the logic you describe is easy to code for, it is also a bit slower -- especially if the date range is long. The code I have posted, while long (it is filled with comments :) ), has successfully been in use by many, and has been tested as faster than the looping you are...

>> Just a quick question concerning this thread...what type of field is in 'tblHolidays'? Is it a date containing a full date or a text containing only the month/day? << tblHolidays is a table with the following stucture: tblHolidays ---------- HolidayDate (Date/Time, Unique Index) <any...

... I replied in your other thread that seems to be merging with this one :) ... http://www.access-programmers.co.uk/forums/showthread.php?p=902813#post902813

Hello Genisis... >> Why do you call it a bug? << Because Access formats the SQL Statment into an invalid SQL statment. To show this, create your query with the valid syntax ... INSERT INTO [;DATABASE=D:\rommelfiles\Database2.accdb].[Destination] ( ID, Fn, Mn ) SELECT Source.ID, Source.Fn...

Hello David, >> There is no need to seek out some alternative simply because you're upgrading to A2007, which in no way, shape or form requires conversion to ACCDCB format. << Unless, of course, you wish to utilize the features of the new format that are not available in the .MDB format...

I don't have time to expand now ... but ... that is essentially a bug. If you SAVE the statement in the syntax I have shown, the don't edit it, you *should* be fine ... even if you VIEW the formatting done by MS Access's infinite wisdom :) ... but as soon as you edit anything on the query...

Ok ... I see from your other post that you are using .ACCDB format. But ... I wanted to make sure you knew that the Access 2007 application supports replication IF and only IF, the file format used is .MDB ... I replied to your other thread with an insert syntax that is probably more workable...

I would suggest that you use the following syntax to reference the destination database and table: INSERT INTO [;DATABASE=D:\rommelfiles\Database2.accdb].[Destination] ( ID, Fn, Mn ) SELECT Source.ID, Source.Fn, Source.Mn FROM Source LEFT JOIN...

- How do you keep track of authorized users? - Do you want to send/emain/install a unique authorized version to each person? - Are your tables accessible via a network?

.... hmmm .... I am no seeing where 5 days buisness days added to 10/24/2009 is 11/2/2009 ... 10/26/2002 = Day1 10/27/2002 = Day2 10/28/2002 = Day3 10/29/2002 = Day4 10/30/2002 = Day5 ... Oh ... those are TRANSIT days, so delivery will be the next buisness day, 11/2/2009 ... right? Here...

I think you will need to give us more to go on, like what is your intent ... I know you want two db's to be same, but to what degree ... for example, do you want them as close to real time as possible? ... Which one is the master? ... Also, do take note that Replication is file format...

Chris ... >> who in their right mind would use A2K help if they had A97 help? << No kidding, definately the most helpful help was the A97 help system, seems to be written by people who wanted to help database developers. I do like the A2003 system as well, but A97's system still edges out...

Hello Chris Thanks for the clarification ... eitherway, with the hidden reference, it is completely possible to code in such a way to NOT require an explicit reference to DAO, as you pointed out earlier in the thread. I just used variables declared as objects, where as you did not to use...

You could do a CrossTab query using the summation query that gives you the vertical results. A CrossTab will take this: Sum of Sales Month £30,000 10 £29,000 9 And transpose it to (the | is the column separator): 10|9 £30,000|£29,000 ... Or ... you could get fancier on your query if you...

>> Read the earlier posts, these are shared files on a network drive, << You are headed for corruption with the process you have implemented. >> In tests, users logging in from both OS's at the same time have not had any issues, (no idea why) and when they exit the references are set to...

You CAN late bind to DAO ... sad thing is, you need to know what version you want to late bind to. 'Prepare the JET db engine to do its thing. Set jetEngine = CreateObject("DAO.DBEngine.36") Set workSpace = jetEngine.CreateWorkspace("#DEFAULT#", "Admin", "") Set db =...

NP ... I hope you find the utility useful. If you have any questions regarding it, please feel free to ask.

If the tables are structured in which the values to be compared are ROWS and not columns, then a simple INNER JOIN on the common fields will provide you a resultant set that has the values that are common to both tables .. SELECT tblA.*, tblB.* FROM tblA INNER JOIN tblB ON tblA.Field1 =...

Hopefully you have a split configuration in with there is a Front End (forms, reports, queries, code, and LINKED tables) and a Back End (data tables only) ... with the intent of having EACH user having THERE OWN copy of the Front End .... With that being the premise, then simply make a copy of...

Hey smiler44 ... Like Boyd says ... we need a lot more info ... but ... I will take a stab at it anyway. First off, note that VBA is single threaded, so it can only do one thing at a time. With that, you will probably need to make use of a module variable, and the DoEvents command ...