Search results

I suspect the facility of saving design changes at run time was meant above all for projects where controls are built dynamically during a session. Cheers, Jiri

Hi, have you tried to find out what the path name looks like by putting a watch on it and break the code before the error occurs? Incidentally, you may be better off referring to your path as Application.CurrentProject.path which takes care of the possibility the path changes with different...

Check this, https://stackoverflow.com/questions/3560173/store-arabic-in-sql-database Best, Jiri

Hi, I checked my subforms referencing guide (which has yet to let me down) : http://access.mvps.org/access/forms/frm0031.htm, and if I read your design correctly you might want to try a small change in notation: =DLookUp("Unit","tblData","Category='" & [cboCategory] & "' AND Stage='" &...

You can check the valid form by placing this into the form's BeforeUpdate event. You might need further checking for numeric validity, but this provides the basic test you are asking for. Sub Form_BeforeUpdate(Cancel As Integer) Dim i as Long i = Len(Me!Dimensions) -...

Generally speaking, data checking for all fields is best done via the form's BeforeUpdate event. This event is triggered automatically when you attempt to step off the record or by a save command. See here for examples how to verify that entries on the form are valid. As for highlighting...

Should be: If DatePart("m", CounterBack) = DatePart("m", Me.cboStart) Then Best, Jiri

This error sometimes happens if your Control Source (on the Properties Data Tab) does not agree with the Name (on the Properties Other Tab). Specifically, you need to refer to the Mil_Lic field by its "Name" ! Don't know if this you problem but check anyhow! Best, Jiri

I get this message sometimes when I copy a db to a different machine with a different (,usu lower,) version of Access. It looks scary but it goes away when I decompile and recompile the Front End. Best, Jiri

Obviously, you have to use a routine to find the current back end to your database, if that is where your resource files are. Here is my clumsy way of doing it: Public Function GETBEPath() As String Dim strConnect As String, lngPos As Long strConnect = GetConnectString '...

Assuming that the Date is correct format ("mm/dd/yyyy") then the above red edits should fix your problem with the do loop. Not sure if that is the end of your problems. Best, Jiri

You are welcome.

Hi, the simplest way I know to handle "resource files" (if that is what they are) is to have them in directories relative to the database location. Then when you move the database (the Front End I assume) you move the resource files into the same relative location. You do not have to...

Hi Frank, whenever I run into the "unrecognized format" issue after I port my app into a new machine, newer OS or Access version the first thing I do is decompile and recompile. This usually fixes it. I don't know if this will solve your problem, but if you hadn't already give it a try...

Yes, that's the idea ! Best, Jiri

Probably, the red is your problem. It's not a field name... Best, Jiri

Not knowing your setup, I am not sure. Normally, the matching of the vendor/job (partdesc code, purchase price(?)) would be done through purchase order module. Best, Jiri

Hi, a lot depends on what you use to download data. What would be the input dataset:Excel, CSV,... ? Then, since you say that the "dummy" key - manually inserted, I assume - will identify the job and the customer (youself that is), it should be a cinch to filter it and append the relevant...

Good for you Colin. I don't think you are getting it, though. It does not matter one whit how many clients the app has or how many paths to the BE they have. As long as each workstation at each location has a way to find its own path to the BE (independent of the FE current links) what I have...

I have developed a variation of this which handles this slightly differently. I just leave whatever BE reference there is in the new FE. When the new FE runs, and the reference to BE is incorrect, it will cough up Error 3044 (Invalid Path). Since you need to test a "network down" situation...