Search results

Stay away from Office365.A2013!!! In an another post, I have listed all the dropped feature: they are major!!! Anyway, check my signature. Strangely enough, today it is impossible to open the links proposed...

How do you plan to handle the bar codes? Do you have a BC reader DLL?

Maintenance will be easier and your app will be well organised...

Tested it yesterday using a shortcut from a second user on my Lap and it worked. Can't do a full test because MS complains about Office 2007 residue still present in my system...

I knew there was duplication!!! Create a 4th group and store in it any shared object...

@Paul: one has to be very careful with the PATH since that's the only thing that is saved. Anyway I will check this later this afternoon...

I don't understand why you don't keep the folder structure identical on both PC but that's another story. Here is what I do: 1 - Create a folder MyApplication 2 - Open this folder and create 2 new folders: FE and BE 3 - Save proper files. Now add MyApplication to the Trusted Location...

Create 3 groups of object (navigation pane, personalized) then, after importing the objects of a FE, store them in the proper group. This way you keep the original grouping!!!

Open your DB options then select current db and finaly unselect navigation pane.

Create a table with 2 fields: an auto and a date. When closing the app, add a record to store date/time of closing.

Sol. #2 is the best. One way to avoid complexity, is to keep your 3 menus and make one that links to them...

Here is MY version off your command button: Private Sub CmdLogin_Click() On Error GoTo Erreur If IsNull(Me.txtUsername) Then MsgBox "Please enter Username", vbInformation, "Username Required" Me.txtUsername.SetFocus GoTo ExitProc End If If...

Did you read #14? In the user table add a UserPerm field that YOU and only you can set set. As it is, I suspect your sub sub is bugged. I will have a look at it and will be back...

@RanMan #2: I'm sure there is a typo: you most certainly meant Indecent db. @Plog #10: I check the reference and found no mention of your dogma; to me, case closed... Create a NEW table in your db (ex. ThisIsTheNonLinkedTask_Table?). You have circular relations: that's a major design flaw. Do...

@Plog: Any reference about this one? (Not the it's well known kind of stuff) @Misiek: Why do you need to have 2 DBs? What is DB #1 and DB #2, they have names don't they... T_qa has several useless fields: attach the full screenshot of your DB. Your new table is not normalized...

Oh là là! What a case... 1 - Split your app so that you have a front end (FE) that contains everything except the table. 2 - Create as many BE as needed: only transfer chunks of 500 000 records. 3 - Link the FE to the BEs. 4 - Learn to use VBA to access tables. Why do you want to split your...

2 major points: 1 - Remove the spaces in table and field names: this will simplify you query; 2 - Attach you DB relationships. Otherwise I cannot help...

What's the difference between Allparts and Parts tables? You don't need lookup in a query: table relations do the job.

Definitely not: table location is a property of the table link. Access will handle that auto.

@Spike: someone in this forum warn (threaten) me about my very direct language about O365. It is a catastrophe and MS knows it damn well! I have spent hours on phone with so called experts. First they deny the existence of the problems and when offered to connect to my PC they switch to an angry...