Search results

but I can't change my employer's mind: it's time to find another job...

@Very Doc: Your knowledge is like jam: you spread it at large but too much is too much. You know nothing about the plant where I was working but you have an opinion: oh wowwww! By the way, it was using microwave, a very stupid choice for that kind of industry: foundry and high temp...

@MarkK: a previous post made me think of those new vba statements: if the user does something then update the logout record to Now() + 10 minutes else goto Hell end if :p

You don't need any composite key. You will notice, in the attached schema, that the flow of info. is simple and clear. I linked Payments to Invoices tough I know for sure that they should be linked to the Suppliers in order to deal smoothly with payments error (over/under payments).

@CJ: the problem is that to me, English is a second language. So it may explain why my posts are not perfectly clear. But what about my point on transmission error? It happened to me at Domfer (my last job - now I'm retired) and the only solution I could find was to install optical fiber...

@Melinda: not the close event but the hidden form timer event. When it's done check for a conventional close time, say 5:12:12345 PM. At log in, user is inform of the closing time and once the timer detect that time a modal message with a timer warns the user: no acknowledge after say 5 min...

@Melinda: I understand your need to monitor app usage since I had to do it for a very large app. I suggest creation of an 'empty' logout record while creating the login one. Then, using the timer suggested, update it say every 15 min. including an auto shut down (with message - thing of...

@Doc: Isn't it what I said in post #2? Anyway, if it's a transmission error, I doubt you will find anything in logs since any major event would have affected the network more deeply...

@MJdeMaris: did I use French somewhere? The Choice function was left because I am lazy. I made a Nutrition app that can 'speak' French, English, Spanish and Portuguese. This coding is a way to localise what needs to be translated. No macro can perform the somewhat complex tasks of the...

This method will always work report open or not: DoCmd.OpenReport "ReportName", acViewPreview, , , acHidden Reports!ReportName.Filter = "RecordID = " & RecordID Reports!ReportName.FilterOn = True DoCmd.OpenReport "ReportName", acViewPreview Good luck, JLC.

OK Spike you have the last word. Case closed!!!!

Well, did you read post #9? Do you want screen shuts of what I say? The problem is definitely with, at least, Office 365 Personal's version of Access. Balcom can perform automation but didn't answer yet as what version, package, etc. he is using.

Were you using Office 365 Personal?

@RanMan post #2: beware I bought this think and found it's lousy piece of scrap. Since the guy is parked in Hainan, I plan a trip to China to kick his butt...

@Steve: yes. Create a scheduled job that will start your Access app auto. at power on. Create a default (on start) proc or form that will do both: display a warning message and sending an Email. If you are not using the app, someone must (isn't it) so do the same on that PC.

@Paul: Oh yes I do. I tested this: Dim app As Access.Application Set app = New Access.Application app.OpenCurrentDatabase ("C:\Users\JLCantara\Desktop\Nutrition\Système\NutriSys\NutriSys.AccDB") The app exists and is part of a big nutrition system. I get error 7866: checked on the web...

To further prove MS bad faith, consult Should I create an Access app or an Access desktop database? when creating a new desktop app. 1 - Your organization is not using SharePoint or your Office 365 plan does not include SharePoint Online. Even with PowerPoint, you still can create desktop app...

@RanMan: not sure MS cancelled my A2007 license. @Poooooor GBalcom, you got screwed by MS (so I did). You will find that A2013 doesn't support automation, Activex controls and events of reports. Actualy, MS his imposing PowerPoint DB and will gradually force people to move to it. On top of...

That's most probably a transfer error: don't forget that parity is not checked since Jurassic park. So when something like that occurs, well too bad for the user...

@Gemma Not at all: I really tough there was a neeeeeew version of Access. There are at least 2 version of Office 2013: professional and professional plus. As said by vba somewhere above, it is clear that MS is forcing Access developers to use SharePoint: so bye bye automation, Activex controls...