Encapsulate the field name in square brackets
[Parent UUID]
and in the future do not use spaces in field or object names as it simplifies things if you don't.
Encapsulate the field name in square brackets
[Parent UUID]
and in the future do not use spaces in field or object names as it simplifies things if you don't.
Well, at least you got something working the way you wanted. Good to hear :)
Why not just save the union query and use it in another query for your calculations just like using another query.
What is the code that you currently have tried?
I personally have always used a DTS package to do this (SQL Server 2000)
Since this is 19 days old, you probably already got an answer elsewhere or figured it out, but here's a sample that might help:
Cascading Combo Sample
You would likely need to use subforms, especially if there are any one-to-many relationships.
Oh, I didn't notice it was yours :)
The answer to your original question as to why the query wasn't working is that you never gave it a WHERE clause to limit what it was doing.
Split the database and give each user a copy of the frontend. Multiple versions working in the same db file can only lead to corruption, as well as behaviour you describe here.
See here for more about that:
http://members.shaw.ca/AlbertKallal/Articles/split/index.htm
You really need to split the database and have each user have a copy of the frontend on their machine. See here for more about that:
http://members.shaw.ca/AlbertKallal/Articles/split/index.htm
Also, if you don't want to have to worry about distributing the frontend to each user each time you make a change to the frontend, if you use my Frontend Auto Update Enabling tool, it will enable you to do auto updates of your frontends. Yes, the first distribution you will need to get it to people somehow and that is in your court. But, if you have enabled auto updating, then you can just go into your master file on the network, make your changes, change the version number in two tables (one in the frontend and one in the frontend that is linked to the backend), then when your users open their frontend and the version numbers don't match it will tell them that their frontend is out-of-date and it will close, delete the old file, copy the new file, and then reopen for them automatically.
I had to create this for a big healthcare provider I worked for which originally had over 100 users using a single mdb frontend on the server and they wondered why it crashed each week, or several times each week. So, once we implemented this and moved to frontends on each user's machine, they never had a corruption issue again as long as I was there.
That is available here:
Check out my sample here:
http://downloads.btabdevelopment.com/Samples/listbox/SampleSelectReportFromForm.zip
I'm using this one (actually the Access 2007 version) http://www.amazon.com/Beginning-Access-2003-VBA-Programmer/dp/0764556592/ref=pd_bbs_sr_2?ie=UTF8&s=books&qid=1214204228&sr=8-2
To teach a beginning VBA class for our Portland Access Users Group. It seems to be pretty good.
PLz checj my above procedure for listbox & reply where I m going Wrong.
The very first thing you are doing wrong is using LOOKUPS at the table level. Wrong, wrong, wrong, wrong, wrong....Can you tell I think it's wrong?
See here for more info about that:
The Evils of Lookup Fields at Table Level
It's okay to do lookups at FORM level, but you really should avoid lookups at the table level. It will only cause you pain and suffering later.
To add a form header or footer you can go to VIEW > FORM HEADER/FOOTER
or
VIEW > PAGE HEADER/FOOTER
Export the data using Access, then use the application to open that.
Not to disparage your attempt at a solution MidiMagic, but doing that would not solve the problem of creating a database program without the Access Interface. The questions I have about your suggested solution, are:
1. Export to what?
2. How do you take all of the functionality of the forms and queries and rebuild it in what?
Sure you can build a VB, VB.NET, C#, C++, Java application that is a database application but I don't think that's exactly what they are looking for. Maybe it is, but the indications are that they just don't want to see the Access splash screen and Access application window.
It's possible your auto updates updated your Access 2003 to Service Pack 3 and that has some wonky things going on with it. If you find yourself on SP3 be sure to apply the Access 2003 Post SP3 hotfix.
Microsoft Access lo... how is it?? MS Access provided interface and database.. i jz dunno how to convert it to open the designed interface with no need open MS access
There are some third party tools out that will help you convert an Access app to VB or VB.NET but you really can't just "convert" an Access application to an executable.
If you are using Access 2007, you CAN use the Runtime version of Access and the free developer's kit (search for Access 2007 SDK on the Microsoft Site) and you can distribute the files, including the Runtime version via an installation package.
However, you will still have the Access window and you will need to provide "bullet-proof" error handling and custom toolbars/Ribbon for your users.
U all r talking in this thread abt the form In MS Acess or anyelse.
We weren't talking about a form. We were talking about a function. You should probably post a new thread for your questions.
I guess you'd have to add an:
If dblNumber 1 = dblNumber2 Then
FindLargestNumber = dblNumber1
End If
or you can assign it whatever value you want.
This is roughly what you want. Don't know what you want for the result so I returned the value that was the largest.
Option Compare Database
Private Sub cmdCompare_Click()
MsgBox "The largest number is " & FindLargestNumber(Me.Text1,Me.Text2)
End Sub
Public Function FindLargestNumber(dblNumber1 As Double, dblNumber2 As Double) As Double
If dblNumber1 > dblNumber2 Then
FindLargestNumber = dblNumber1
End If
If dblNumber2 > dblNumber1 Then
FindLargestNumber = dblNumber2
End If
End Function
Hello. I'm working on a similar project. Is it possible to have the results returned in another form, Rather than a report? I want to do a Date range search and then be able to edit the data in my resulting records. Thanks
Yes, you would do similar to what was shown for the report but base the criteria of the recordsource of the other form as shown above.
Check out this report sample here on my site. It shows you how to set the criteria for reports from a form:
http://downloads.btabdevelopment.com/Samples/combos/FormSampleFromMultipleCriteria.zip
It isn't exactly the same as what you are looking for, but it should get you on the right track.
That would be:
TOOLS > ANALYZE > DOCUMENTER
To install as Administrator, right-click on the setup file and select RUN AS ADMINISTRATOR.
Looks like Access 2003 and earlier don't have that feature, and there are multiple Office Marketplace apps for sale.
Don't have what feature? The documenter is available in 2000 to 2007 I know that as I have them.
Make sure when you go to install your drivers, that you run the install as Admin because in Vista, if it is changing configuration and it isn't Microsoft Software, it doesn't always let the software install unless it is certified by Microsoft UNLESS you run the install as admin.